Skip to main content
Glama

Ask Bestie Cars

Compare car popularity

compare_products
Read-onlyIdempotent

Compare 2–5 model groups by registration share and trend in Sweden. Current SEK pricing appears where verified; no performance or safety verdict.

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
productsYesProduct ids or names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world behavior, so the description's added value is the data caveats: pricing is only shown 'where verified' and no performance or safety verdicts are produced. Those disclosures set expectations about incomplete or absent fields, which is exactly what an agent cannot infer from structured fields. It stops short of describing ordering or return shape.

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

Conciseness5/5

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

Two short sentences, zero filler, with the core operation and scope front-loaded and the caveats trailing. Every clause carries distinct information.

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

Completeness4/5

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

For a one-parameter read-only comparison tool, the definition covers scope, data availability, and output limits, which is sufficient to call it correctly. Minor gaps remain around result ordering and whether missing models error or are dropped, but no output schema exists to cover them.

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 coverage is 100% and the single parameter's description ('Product ids or names') matches what the prose implies. The '2–5 model groups' phrasing merely restates minItems/maxItems already declared in the schema, so no meaning is added beyond the schema.

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?

States a specific verb and resource ('Compare ... model groups') plus the exact comparison basis (registration share and trend) and the market (Sweden). The 2–5 arity implicitly separates it from single-product siblings like get_product, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the bounded scope (2–5 items, Swedish registration data), which tells the agent this is a multi-item comparison rather than a lookup. There is no explicit when-to-use/when-not guidance or pointer to an alternative such as search_products or best_in_category.

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