Retrieve a list of products from the BeezUP merchant catalog by submitting a request body.
Get product list
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": "Catalog_GetProducts"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Request body |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, authentication requirements, pagination, or response size. The description carries the full burden but fails entirely.
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 extremely short (three words) but is under-specified rather than concise. It lacks essential information and does not earn its place as a complete description.
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 complexity of the tool (one nested object parameter, no output schema, many sibling tools with similar names), the description is woefully incomplete. It does not explain the body, response, or how to use the tool effectively.
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?
The input schema has one parameter 'body' described as 'Request body', which is minimally informative. The tool description does not elaborate on what the body should contain, despite the schema coverage being 100% but vague. The description adds no meaningful parameter guidance.
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 product list' provides a verb and resource, but it is vague and does not distinguish from sibling tools like Catalog_GetProductByProductId or Catalog_GetRandomProducts. It fails to specify the scope (all products? filtered?) or whether it returns a full catalog or a summary.
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 is given on when to use this tool versus alternatives (e.g., Catalog_GetProductBySku, Catalog_GetCategories). There is no context on prerequisites, exclusions, or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.