cf_search_categoriesSearch categories by name and get their taxonomy path. Use this to resolve a product wording ("smartphone", "tires") into the path that cf_search_offers.categories expects.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query for category name | |
| limit | No | Max results |
| Name | Required | Description | Default |
|---|---|---|---|
| categories | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds behavioral context by explaining the output is a taxonomy path and how it integrates with cf_search_offers, going beyond the structured annotations.
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 two concise sentences, front-loaded with the core purpose and immediately followed by a concrete use case. No wasted words.
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 rich annotations, fully documented schema, and presence of an output schema, the description covers the essential workflow purpose and integration with a sibling tool. It is complete for this tool's complexity.
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 coverage is 100%, so the baseline is 3. The description adds semantic value by explaining that 'q' can be a product wording like 'smartphone' or 'tires', giving the parameter real-world context beyond the schema's generic 'Search query for category name'.
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 tool searches categories by name and returns their taxonomy path. This distinguishes it from sibling tools like cf_list_categories (listing all) and cf_category_hierarchy (hierarchy), using a specific verb+resource+output pattern.
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 explicitly states when to use the tool: to resolve a product wording into a category path for cf_search_offers. It implies when not to use it (e.g., when listing all categories), but does not explicitly name alternative sibling tools, so it falls slightly short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes, particularly cf_category_hierarchy vs cf_list_categories (both provide category taxonomy paths) and cf_search_offers vs cf_list_offers (both return offers). Descriptions help, but the boundaries between category-related tools and offer listing/search could confuse an agent.
All tool names follow a consistent cf_ verb_noun snake_case pattern (e.g., cf_add_wish, cf_list_retailers, cf_search_offers). The convention is uniform and predictable, making it easy to infer tool behavior from the name.
With 22 tools, the server covers a broad domain but is slightly heavy. The count is reasonable for a price-comparison service with search, product, price, retailer, user, and comment functionality, though it exceeds the typical ideal range.
The toolset provides solid coverage of the price-comparison domain: search, categories, offers, products, retailers, price history/summary, deal analysis, wishlist, comments/reviews, and user search history. Minor gaps exist (e.g., no product-specific reviews, no comment edit/delete), but core workflows are fully supported.