Skip to main content
Glama

Compare vendors

compare_vendors
Read-onlyIdempotent

Two to five vendors side by side: starting price and what it covers, areas, event types, deposit, booking lead time, cancellation policy and how to book, with every fact's source. Use it when a consumer is choosing between vendors from a search or shortlist.

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": {
      "vendors": "<vendors>"
    },
    "name": "compare_vendors"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorsYes2 to 5 vendors, each a name, index_page URL or slug.

Output Schema

NameRequiredDescriptionDefault
cite_asNoAgent Bookability Index by The Runup (index.therunup.ai)
vendorsYes
side_by_sideYesOne row per vendor with the facts most used to choose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: the output is a sourced comparison where every fact carries its provenance, and the input is bounded at two to five vendors. It does not discuss failure modes for unresolvable vendors, which keeps it from a 5.

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?

Two sentences, front-loaded with what the comparison returns before the when-to-use clause. The attribute list is long but each item is a genuinely distinct compared field rather than filler. Minor cost: the list is dense in a way that slightly buries the usage sentence.

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?

With an output schema present, the description need not explain return structure, and it still summarizes the returned dimensions and their sourcing. Annotations cover the safety profile and the single parameter is fully documented. Only edge-case behavior (invalid or duplicate vendor entries) is unaddressed, which is a small gap for a read-only tool.

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?

There is only one parameter and schema coverage is 100%; the schema already states '2 to 5 vendors, each a name, index_page URL or slug.' The description repeats the two-to-five bound and adds no new syntax or format meaning. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource ('Two to five vendors side by side') and enumerates exactly what is compared: starting price and coverage, areas, event types, deposit, booking lead time, cancellation policy, booking method, plus per-fact sourcing. That is far more specific than the title. It stops short of naming a sibling tool, so the differentiation from search_vendors/get_vendor is only implied by the workflow phrasing.

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

Usage Guidelines4/5

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

'Use it when a consumer is choosing between vendors from a search or shortlist' gives a clear triggering context and implicitly positions this as the step after search/shortlist. There are no explicit exclusions (e.g. what to do for a single vendor or more than five), but the context is unambiguous.

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