Retrieve Tally products using filters for category, search, price range, and sorting. Locate specific items or compare deals by querying product data with pagination.
Retrieve products with optional category/search/price filters.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| token | No | ||
| search | No | ||
| sortBy | No | ||
| category | No | ||
| maxPages | No | ||
| maxPrice | No | ||
| minPrice | No | ||
| pageSize | No | ||
| accountId | No | ||
| locationId | No | ||
| maxRecords | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-style retrieval, but omits important behaviors such as pagination via token, maxPages/pageSize handling, sorting, and what the response contains.
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 a single efficient sentence with no filler. It front-loads the core purpose and filter types, though it could have used the available space to add more value.
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?
For a 12-parameter tool with no annotations and no output schema, this description is incomplete. It does not explain pagination, sorting, token usage, or response shape, leaving an agent under-informed for correct invocation.
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%, so the description must compensate for 12 parameters. It only clarifies category, search, and price filters, leaving limit, token, sortBy, maxPages, pageSize, and other parameters semantically unexplained.
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 clearly states the action (retrieve), the resource (products), and the available filter dimensions (category, search, price). This is specific enough to distinguish it from list_categories, though it does not explicitly contrast with ask_products.
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?
The description offers no guidance on when to prefer this tool over alternatives like ask_products or list_categories. It implies this is the tool for straightforward product listing, but does not state exclusions or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.