Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

api_find

Read-only

Search the full WebCake backend API to find operation IDs and call details for endpoints not covered by dedicated tools, then use the returned IDs to make calls.

Instructions

Search the FULL WebCake backend API (675 operations the storefront account can call — far more than the dedicated tools cover). With query: one line per match id — Controller.action (body/query keys, * = required) ⇒ tool: dedicated tool if one exists. With id: the call sheet (path params, body/query keys with their nested fields, required keys, permission needed). Prefer a dedicated tool when one is listed; use api_get / api_call for the rest.

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": "api_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoExact operation id from a previous search, e.g. 'post:/api/v1/dashboard/site/:site_id/products/create'
limitNoMax lines (default 15)
queryNoEnglish keywords from the path/controller, e.g. 'shipping fee', 'product tag', 'customer point'
methodNoOnly this HTTP method

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely new context beyond that: the scope (675 operations, broader than dedicated tools), the exact line format returned in query mode, and the contents of the call sheet in id mode including permission requirements. It stops short of pagination or rate-limit behavior, which keeps it at a 4.

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?

The scope statement is front-loaded and the two modes are laid out in parallel clauses with no wasted sentences. The telegraphic format with embedded arrows and asterisks is dense but readable for an agent.

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?

With no output schema, the description carries the return-shape burden and does so for both modes. Combined with full schema coverage and a readOnly annotation, an agent has what it needs to call this correctly; only the query/id exclusivity and the sibling search_tools relationship are left unstated.

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, and the baseline is 3. The description does add mode-level semantics — query returns match lines, id returns a call sheet — which is meaningfully more than the schema's per-parameter text, but the relationship between query and id being mutually exclusive is only implied.

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?

The description states a specific verb and resource ('Search the FULL WebCake backend API', 675 operations) and explicitly positions itself against both the dedicated tools and the api_get / api_call fallbacks. An agent can distinguish this discovery tool from its siblings without opening the schema.

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 gives clear routing rules: prefer a dedicated tool when one is listed, and use api_get / api_call for everything else. It also distinguishes the two invocation modes (query for discovery, id for the full call sheet). It does not clarify the boundary with the search_tools sibling, which is the one remaining gap.

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