Skip to main content
Glama

Ver el viaje armado

trip_view
Read-onlyIdempotent

Show the trip trip_id as it stands: legs, nights, chosen flight and hotels with their WizTrip prices in USD, the total, what is still missing and, when it can be booked, the card's «Reservar ahora» button. Does not talk to Wizzo.

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": {
      "trip_id": "<trip_id>"
    },
    "name": "trip_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
trip_idYesThe trip id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is covered. The description adds real context beyond that: it is a snapshot of current state, prices are in USD, it reports what is still missing, and the «Reservar ahora» button only appears when booking is possible, plus it clarifies it does not invoke the chat assistant.

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?

Front-loaded with the verb and resource, followed by a compact enumeration of returned content and a short boundary sentence about Wizzo. The enumeration is dense but every item conveys something the agent needs; nothing is filler.

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 no output schema, the description carries the burden of describing return values and does so thoroughly (legs, nights, chosen flight/hotels, USD prices, total, missing items, conditional booking button). For a one-parameter read-only snapshot tool this is close to complete; only error/empty-trip behavior is unaddressed.

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 a single parameter with 100% schema coverage, so the baseline is 3. The description references `trip_id` and frames it as the trip whose current state is shown, but adds no format or provenance detail beyond the schema's 'The trip id.'

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 ('Show') and resource ('the trip `trip_id`') and enumerates exactly what the view contains: legs, nights, flight, hotels, USD prices, total, missing items and the booking button. It never names a sibling tool explicitly, but 'Does not talk to Wizzo' implicitly separates it from trip_chat.

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 phrase 'as it stands' (a read-only snapshot of the currently assembled trip) and by the exclusion of Wizzo chat. There is no explicit when-to-use/when-not statement and no named alternative such as trip_choose for making changes.

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