Skip to main content
Glama

Search marketplace API

search
Read-onlyIdempotent

Searches the OpenAPI spec of this organization's marketplace APIs. Use it before execute to find operations and their parameters.

Write an async arrow function that returns the result. await codemode.spec() returns the OpenAPI 3.1 spec with $refs resolved inline: spec.paths[path][method] is an operation with summary, description, operationId, tags, parameters, requestBody, responses and the extensions x-write, x-async, x-rate-limit and x-body-encoding. spec.info.description has the connections and platform notes. Return only what you need, not the whole spec.

Example: async () => { const spec = await codemode.spec(); const hits = []; for (const [path, ops] of Object.entries(spec.paths)) for (const [method, op] of Object.entries(ops)) if (/order/i.test(${path} ${op.summary ?? ""})) hits.push({ method: method.toUpperCase(), path, summary: op.summary }); return hits; }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesJavaScript async arrow function to search the spec
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the `codemode.spec()` SDK call, that $refs are resolved inline, the operation/extension shape of `spec.paths`, and that `spec.info.description` holds connection and platform notes. It also advises returning only the fields needed, which is real behavioral guidance for a code-execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, followed by mechanics and then a compact example; every part carries information. The example is somewhat long relative to the surrounding text, but it earns its place by demonstrating spec traversal for a code-generation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a code-execution search tool with no output schema, the description effectively documents the return surface (spec.paths, operation fields, extensions, spec.info.description) and the result-shaping expectation. The only residual gap is that it does not state whether other `codemode` helpers exist or that the function's return value itself becomes the tool result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining what the `code` parameter's function actually operates on — the `codemode.spec()` object and its traversal shape — plus a worked example. It does not clarify the `context`/`conversation_id` params, though the schema already documents those thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the OpenAPI spec of this organization's marketplace APIs") and explicitly distinguishes itself from the `execute` sibling by positioning itself as the discovery step that precedes execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it before `execute` to find operations and their parameters" gives clear sequencing guidance relative to the one alternative that matters. It never states a when-not case (e.g., skip if you already know the operation), so it falls just short of fully explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.