Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

api_get

Read-only

Run a read-only GET API operation by api_find id, trimming list results with pick and max_items; rejects non-GET requests.

Instructions

Run a READ-ONLY (GET) operation from api_find by id. site_id is filled from the current site. Use pick / max_items to keep the result small. Refuses anything that is not a GET.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOperation id from api_find (preferred)
pathNoCatalog path with :params, e.g. /api/v1/dashboard/site/:site_id/product_tags/all
pickNoKeep only these fields on each item of a list result (or on a single object)
queryNoQuery-string values
methodNoWith path, when id is not given
max_itemsNoCap list results (default 50)
path_paramsNoValues for :params in the path; site_id defaults to the current site

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety, and the description adds useful behavior: site_id is automatically filled from the current site, non-GET operations are rejected, and pick/max_items should be used to limit result size. It does not discuss response shape, authentication, or rate limits, but it adds meaningful context beyond the annotations.

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?

The description is four short sentences, front-loads the core action, and contains no wasted wording. Each sentence contributes either purpose, context, result-size guidance, or the GET-only restriction.

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 generic API execution tool with seven documented parameters and a read-only annotation, the description covers the main invocation path and key constraints. It does not explain the return shape or the path/method fallback when no id is supplied, but the schema covers parameter details and the tool's output depends on the selected operation.

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 description coverage is 100%, so the schema already explains the parameters in detail. The description reinforces the id/site_id relationship and the purpose of pick/max_items, but adds little parameter semantics beyond what the schema already provides.

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: run a read-only GET operation identified by an api_find id. It clearly distinguishes this from broader API-call tools by restricting the operation to GET and rejecting anything else.

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 context that the operation should come from api_find by id and explicitly says non-GET operations are refused. It does not name the alternative tool to use for non-GET operations, so it stops short of fully explicit routing guidance.

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