Skip to main content
Glama

compare_trips

Compare 2 to 4 trips by slug: side-by-side attributes plus grounded per-traveller-type verdicts (same logic as the site's compare pages).

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does disclose the return shape: side-by-side attributes plus per-traveller-type verdicts, with 'grounded' signalling the verdicts are evidence-based rather than invented. It says nothing about read-only safety, behavior for invalid or duplicate slugs, ordering effects of the slug list, or errors, which leaves meaningful behavioral gaps.

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?

A single front-loaded sentence with the key constraints up front and no filler. The parenthetical site reference is slightly incidental but short enough to earn its place as a fidelity cue.

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

Completeness3/5

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

For a simple read-style tool with no output schema the description covers the gist of what comes back and the input bound, which is the core need. It is still incomplete on edge cases (invalid slug, duplicate slug, output ordering) and on the safety profile that annotations would normally supply.

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 0% for the single 'slugs' array, so the description must compensate; it adds that the items are trip slugs and that 2-4 are expected, reinforcing the schema's min/maxItems. It does not explain slug format, whether duplicates are allowed, or what happens when a slug does not resolve, so the array's item semantics remain thin.

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 ('Compare ... trips by slug') plus the cardinality bound, so the agent knows exactly what operation is performed. It does not explicitly contrast with the sibling 'get_trip' (single-trip lookup) or 'search_trips', but the multi-trip comparison framing makes the distinction obvious.

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 only implied: an agent infers it should call this when it already holds 2-4 trip slugs and wants a comparison. There is no statement of when not to use it, no mention of the alternatives for one-trip or discovery-style needs, and no prerequisites such as slugs being valid or distinct.

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