Operations: find operations

Find any operation by describing the job, and read its exact input. 2 operations. How to call them, and what the answers mean: Operations reference.

Generated from the operation catalog: src/lib/ops/public-catalog.json in publicsummerengine at 0d85f61e2b and the summer-engine npm package 4.0.0 for engine and local operations. If something here is wrong, the operation’s definition is wrong.

Operation	What it does	Asks you first
`ops.describe`	Read one operation in full by its name (or a 3.x tool name): input and output schemas, effect, approval, examples.	Never
`ops.search`	Find any Summer operation by describing the job in plain words.	Never

describe

ops.describe: Describe a Summer operation Read one operation in full by its name (or a 3.x tool name): input and output schemas, effect, approval, examples. Next: summer_call.


MCP	`summer_call` with `"op": "ops.describe"`
CLI	`summer ops describe`
Runs	On Summer’s servers: the hosted MCP, or the npm MCP after `summer login`. Needs your Summer sign-in.
Effect	Reads only. Changes nothing.
Asks you first	No. It changes nothing.

Inputs:

Input	Type	Required	Description
`name`	string	Yes	An op name such as pricing.set_base, or a 3.x tool name. Length 1 to 80.

Input JSON schema

{
  "type": "object",
  "properties": {
    "name": {
      "description": "An op name such as pricing.set_base, or a 3.x tool name.",
      "type": "string",
      "minLength": 1,
      "maxLength": 80
    }
  },
  "required": [
    "name"
  ]
}

Result JSON schema

{
  "type": "object",
  "properties": {
    "operation": {
      "type": "object",
      "additionalProperties": {}
    }
  },
  "required": [
    "operation"
  ],
  "additionalProperties": false
}

Example: The exact input of games.list.

{
  "name": "summer_call",
  "arguments": {
    "op": "ops.describe",
    "input": {
      "name": "games.list"
    }
  }
}

summer ops describe --name games.list

search

ops.search: Find a Summer operation Find any Summer operation by describing the job in plain words. Returns the best matches with their exact input schema, effect and approval. Next: summer_call with the name.


MCP	`summer_search`, a tool on the hosted MCP and the npm assets profile. Elsewhere: `summer_call` with `"op": "ops.search"`
CLI	`summer ops search`
Runs	On Summer’s servers: the hosted MCP, or the npm MCP after `summer login`. Needs your Summer sign-in.
Effect	Reads only. Changes nothing.
Asks you first	No. It changes nothing.

Inputs:

Input	Type	Required	Description
`query`	string	Yes	The job in plain words: “lower my game’s price”, “upload a web build”. Length 1 to 300.
`area`	string	No	Only this area: assets, store, pricing, analytics…
`effect`	”read” \| “write” \| “spend” \| “publish” \| “player_facing” \| “destructive”	No
`limit`	integer	No	Default `5`. Range 1 to 20.

Input JSON schema

{
  "type": "object",
  "properties": {
    "query": {
      "description": "The job in plain words: \"lower my game's price\", \"upload a web build\".",
      "type": "string",
      "minLength": 1,
      "maxLength": 300
    },
    "area": {
      "description": "Only this area: assets, store, pricing, analytics...",
      "type": "string",
      "pattern": "^[a-z]+$"
    },
    "effect": {
      "type": "string",
      "enum": [
        "read",
        "write",
        "spend",
        "publish",
        "player_facing",
        "destructive"
      ]
    },
    "limit": {
      "default": 5,
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "query"
  ]
}

Result JSON schema

{
  "type": "object",
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "summary": {
            "type": "string"
          },
          "effect": {
            "type": "string",
            "enum": [
              "read",
              "write",
              "spend",
              "publish",
              "player_facing",
              "destructive"
            ]
          },
          "approval": {
            "type": "string"
          },
          "provider": {
            "type": "string"
          },
          "status": {
            "type": "string"
          },
          "available": {
            "type": "boolean"
          },
          "mcpTool": {
            "description": "Call it directly with this tool; else use summer_call.",
            "type": "string"
          },
          "input": {
            "description": "The exact input JSON Schema for summer_call.",
            "type": "object",
            "additionalProperties": {}
          }
        },
        "required": [
          "name",
          "title",
          "summary",
          "effect",
          "approval",
          "provider",
          "status",
          "available",
          "input"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "items"
  ],
  "additionalProperties": false
}

Example: Find the pricing operation and its input.

{
  "name": "summer_call",
  "arguments": {
    "op": "ops.search",
    "input": {
      "query": "lower the price of my game"
    }
  }
}

summer ops search --query 'lower the price of my game'

Overview

Operations

HTTP API

GDScript API

Migration and extensions

MCP

Operations: find operations

describe

search

​describe

​search

describe

search