Skip to main content
Glama

TravelCargo

Get trip

get_trip

Fetch a single active public trip by id (ids come from search_trips). Returns the same allowlisted fields.

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": {
      "id": "<id>"
    },
    "name": "get_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTrip id from search_trips

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that only 'active public' trips are reachable and that fields are allowlisted, but it does not say what happens for a missing, private, or inactive id, nor does it clarify the referent of 'the same allowlisted fields'.

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?

It is a single tight sentence with the resource and scope front-loaded and no wasted wording. The trailing phrase 'the same allowlisted fields' is slightly ambiguous about what it is the same as, which keeps it from a 5.

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 one-parameter fetch with no output schema and no annotations, the description covers id provenance and the active/public restriction. It leaves the return shape vague and omits not-found or error behavior, which matters more here because no annotations or output schema backfill that gap.

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 one required parameter with 100% schema description coverage, and the schema already states 'Trip id from search_trips'. The description's parenthetical repeats that provenance rather than adding new meaning, so the baseline of 3 applies.

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 names a specific verb and resource ('Fetch a single active public trip by id') and scopes it to active, public trips, which distinguishes it from the sibling search_trips. It stops short of a fully explicit contrast statement, but the single-vs-search distinction is inferable from 'single' plus the id-source reference.

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?

It gives clear usage context by stating ids come from search_trips, so an agent knows the prerequisite workflow. It offers no explicit when-not-to-use guidance and does not mention estimate_quote as an alternative path, so it falls short of the top band.

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