Skip to main content
Glama

Full of Joy · Croatia private tours

Tour details

get_tour
Read-onlyIdempotent

Full details of one tour: options with inclusions and exclusions, languages, duration, page URL and price tiers.

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": {
      "tour": "<tour>"
    },
    "name": "get_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
tourYesTour key from list_tours.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value by listing the returned content categories, but says nothing about error behavior for invalid keys, freshness of pricing, or whether tiers are complete.

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?

One tightly packed sentence that front-loads the resource ('one tour') and then enumerates the payload. No filler, no redundancy.

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 simple one-parameter read tool with rich annotations, the definition is nearly sufficient, and with no output schema it usefully summarizes the returned fields. Minor gaps remain around invalid-key behavior and relationship to check_availability for pricing/live data.

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 description coverage is 100% and the single parameter is documented as 'Tour key from list_tours', which is adequate. The description adds no further meaning about the key format or scope, so baseline 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 resource ('one tour') and enumerates the detail payload it returns (options, inclusions/exclusions, languages, duration, page URL, price tiers), which clearly separates it from list_tours and check_availability. It never states the verb explicitly, but 'Full details of one tour' is unambiguous enough that an agent can tell it is a single-item detail read.

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: fetch details for a specific tour, using the tour key obtained from list_tours (that hint lives in the schema, not the description). There is no explicit when-to-use versus check_availability or request_booking, and no guidance on prerequisites or what happens with an unknown key.

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