Skip to main content
Glama

sb_api_find

Read-only

Find Store Builder API operations by intent or retrieve a full call sheet by ID, including parameters, credentials, body fields, and handler caveats.

Instructions

Find API operations by intent (query), or get a call sheet (id): parameters, credential, body fields and handler caveats. Reaches all 969 operations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sb_api_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAn id from a previous search — returns that operation's full call sheet
tagNoNarrow to one tag, e.g. "menus", "products", "theme"
limitNoDefault 8
queryNoWhat you want to do, in words: "create a menu", "list orders", "upload media"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds context beyond that: the total reachable catalog size (969 operations) and an enumeration of what a call sheet contains (parameters, credential, body fields, handler caveats), which is valuable given there is no output schema. It does not discuss result ordering, relevance behavior of the intent match, or how the limit interacts with paging.

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

Conciseness5/5

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

Two short sentences, purpose front-loaded, with the two modes packed into a single parenthetical rather than separate clauses. The catalog-size sentence is short and adds scope. No filler or repetition.

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 read-only, zero-required-parameter lookup tool with full schema coverage and no output schema, the description covers both entry modes and what the result contains. Gaps are secondary: no note on how query and tag compose, and no mention of result ordering or how to widen a search when the default limit of 8 is exhausted.

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

Parameters3/5

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

Schema coverage is 100%, so all four parameters are already documented, including the id-provenance note and the limit default of 8. The description's 'by intent (query), or get a call sheet (id)' restates that same framing without adding format, matching semantics, or combination rules (e.g. query plus tag). Baseline 3 is appropriate when the schema carries the parameter burden.

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

Purpose4/5

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

The description names a specific verb and resource ('Find API operations') and distinguishes its two modes: intent search via query versus fetching a full call sheet via id. It also states scope ('Reaches all 969 operations'), making coverage unambiguous. It stops short of naming the sibling that actually invokes an operation (e.g. sb_api_call), so differentiation from execution tools is only implicit in the word 'Find' and the 'call sheet' framing.

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?

It clearly routes between the two calling patterns: use query when you can state what you want to do, use id when you already have one from a prior search. That is explicit mode-selection guidance. It gives no exclusions or pointer to an alternative tool for actually running an operation, and doesn't explain what to do when a query returns nothing useful.

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