Skip to main content
Glama

Part Guide AI Catalog

Compare AI products

compare_products
Read-onlyIdempotent

Compare sourced attributes within one shared category.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "products": "<products>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoUTC date for freshness checks (YYYY-MM-DD). Defaults to today.
categoryNoCatalog category ID, such as models or editors
productsYesProduct ids or names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already state this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the shared-category constraint and the notion of sourced attributes, but it does not explain what a comparison result contains or how mismatched categories are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no wasted wording. It is perhaps too terse for the tool's comparison behavior, but the sentence itself is efficient and clear in structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should explain what the comparison returns, such as which attributes are compared or how sources are represented. It does not provide that output context, leaving the agent to infer the result format from the name alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already well documented. The description adds only the implication that products must belong to one shared category, without clarifying how the optional category parameter interacts with that requirement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compare attributes, scoped to one shared category. It is clearer than a tautology and implies a side-by-side comparison rather than search or retrieval, though 'sourced attributes' is somewhat jargon-heavy and it does not explicitly distinguish itself from the sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no explicit when-to-use guidance, no when-not-to-use conditions, and does not name alternatives such as search_products or get_product. The phrase 'within one shared category' implies a constraint but not an operational selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources