Skip to main content
Glama

Get tour details

get_tour_details
Read-only

Get detailed information about a specific tour including full description, pricing and booking URL.

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": {
      "slug": "<slug>"
    },
    "name": "get_tour_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTour URL slug (from search_tours results)

Output Schema

NameRequiredDescriptionDefault
tourYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the response contains full description, pricing, and booking URL, which is useful context, but it doesn't discuss failure modes such as an unknown slug or whether the record can be missing.

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 sentence that front-loads the action and then lists the returned content. There is no filler, repetition, or burying of key information.

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?

For a one-parameter read-only lookup with annotations and an output schema, the description covers what the tool does and what it returns well enough to call it correctly. The only real gap is the absence of explicit routing guidance among the three siblings.

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 100%, and the schema itself explains that the slug comes from search_tours results, so the parameter is fully documented structurally. The description adds no further meaning about slug format or lookup behavior beyond what the schema already provides, making the baseline of 3 appropriate.

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 states a specific verb and resource ('Get detailed information about a specific tour') and enumerates what is included: full description, pricing, and booking URL. It does not explicitly contrast itself with search_tours or submit_inquiry, so sibling differentiation is only implied through the schema's 'from search_tours results' note.

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: the tool retrieves one specific tour by slug, while search_tours presumably discovers tours. There is no explicit statement of when not to use it or which alternative to pick, so the agent must infer the search-then-detail workflow from the parameter description alone.

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