Skip to main content
Glama

compare_options

Compare current retail prices and stock in up to five countries without buying.

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": {
      "service": "<service>",
      "countries": "<countries>"
    },
    "name": "compare_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
serviceYes
countriesYes
max_price_rubNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does carry the important signal that no purchase occurs, plus the hard constraint of at most five countries. It says nothing about authentication requirements (there is an api_key parameter), currency assumptions, or failure modes, so the full behavioral burden is not met.

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?

A single front-loaded sentence with the comparison target, the country cap, and the non-purchase guarantee. Nothing is padded or redundant.

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?

An output schema exists, so return values need not be described, but three of four inputs remain opaque and there are no annotations to fall back on. For a four-parameter comparison tool this leaves the agent guessing about the service identifier and price threshold.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description only adds meaning to 'countries' by capping it at five. The 'service' identifier, the 'max_price_rub' threshold, and the 'api_key' parameter are entirely unexplained in both schema and description.

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 definition uses a specific verb and resource ('Compare current retail prices and stock') and states a scope limit ('up to five countries'). The phrase 'without buying' implicitly distinguishes it from purchase-oriented siblings like buy_number, though 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?

'Without buying' implies this is the read-only price-check path rather than an order path, which is useful implied guidance. However, it never says when to prefer this over get_price or how it relates to list_countries/list_services, so the agent must infer the routing.

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.