Retrieve a list of shops, with optional limit and allowed status filters. Enables access to shop data for retail management.
Get list of shops
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": "billz_get_shops"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| only_allowed | No |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not mention whether the list is paginated, if it requires authentication, or what the 'only_allowed' parameter implies behaviorally.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one sentence), but this conciseness sacrifices utility. It is front-loaded but lacks necessary details, making it under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 2 optional parameters, no output schema, and no annotations, the description is incomplete. It does not cover return format, pagination, or the effect of parameters, leaving significant gaps for an agent to understand the tool's behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the parameters 'limit' or 'only_allowed'. While the names hint at their meaning, no explicit semantics or constraints are given, which is insufficient for proper agent usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get list of shops' uses a verb+resource structure, but it is generic and does not differentiate from sibling tools like billz_get_categories or billz_get_brands. It lacks specifics on what kind of shops are returned (e.g., all shops, user-specific, etc.).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like billz_search_sales or billz_get_categories. No context on prerequisites or typical use cases is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.