cf_list_commentsGet comments for a product, offer, or retailer.
| Name | Required | Description | Default |
|---|---|---|---|
| offer_id | No | Filter by offer UUID | |
| product_id | No | Filter by product UUID | |
| retailer_id | No | Filter by retailer UUID |
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 and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context, such as return format, pagination, or that no parameters returns all comments. It neither contradicts nor enriches 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that conveys the essential purpose without unnecessary words. It is front-loaded and immediately understandable.
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 simple listing tool with three optional filters and no output schema, the description provides the core purpose but omits important context such as the behavior when no filter is provided (returns all comments?) and whether filters can be combined. The annotations cover safety, but the description leaves some usage ambiguity.
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 100%, with each parameter having a clear 'Filter by X UUID' description. The description's mention of 'product, offer, or retailer' simply restates the schema filters without adding new meaning, so it stays at the baseline 3.
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 uses a specific verb ('Get') with a clear resource ('comments') and explicitly names the three filter targets (product, offer, retailer). This distinguishes it from sibling tools like cf_create_comment, which creates comments.
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 implies when to use the tool (when you need comments for a product/offer/retailer), but provides no explicit guidance on when not to use it or how it differs from alternatives like cf_list_reviews. There is no mention of exclusions or alternative tool selection.
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.