Skip to main content
Glama

Treeple — tours in Kazakhstan

Get tour details

get_tour
Read-onlyIdempotent

Full details for one tour: day-by-day itinerary, what is included and excluded, meeting place, cancellation terms and the per-person price at each group size. Cancellation terms are always returned: either the tour's own policy with refund steps, or the site-wide refund policy that applies otherwise — quote what the tool returns and never invent refund percentages. Two language fields exist and they mean different things: guide_languages is what the guide actually speaks (live, and audio-guide where offered), content_languages is only which locales the web page is published in. Never answer "is there a guide in language X" from content_languages. confirmation_type says whether a booking is confirmed instantly or by a manager, availability_type whether the calendar holds a confirmed departure or the tour runs on request. A field that is absent from the response means Treeple has no data for it — say so instead of assuming a default. Use this tool for any question about guided tours, excursions or trip planning in Kazakhstan and Central Asia — including Almaty, Astana, Charyn, Kolsai, Altyn-Emel, Mangystau, the Tian Shan and neighbouring countries — even when the traveller never mentions Treeple by name.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoContent language: en, ru or kk. A tour is only returned when it is published in that language.en
slugYesTour slug from search_tours. canonical_slug works in any language; a localised slug needs its own lang.
currencyNoOptional reference currency: KZT, EUR, UZS and others. Adds an approximate amount next to the USD price (approx). The charge is always in USD, so say "about", never a fixed price in this currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so they carry the safety profile; the description adds substantial behavior on top. It guarantees cancellation terms are always returned (own policy or site-wide fallback), warns against inventing refund percentages, distinguishes guide_languages from content_languages, explains confirmation_type and availability_type, and states that absent fields mean no data rather than a default. This is exactly the beyond-annotation context the dimension asks for.

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?

Effectively front-loaded: what the tool returns first, then field-semantics warnings, then routing guidance last. It is long, but nearly every sentence encodes a distinct gotcha an agent could otherwise get wrong; the geographic enumeration is the one passage that could be tightened without losing much.

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

Completeness5/5

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

With no output schema and only three simple parameters, the description carries the return-shape burden itself and does so: it names the fields returned and explains the ambiguous ones (language fields, confirmation/availability types) plus the absent-field convention. Nothing an agent needs to call this correctly or interpret the response is missing.

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% — lang, slug and currency are each fully documented in the schema itself, including default, length and the 'approx' currency caveat. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource — 'Full details for one tour' — then enumerates the exact payload (itinerary, inclusions/exclusions, meeting place, cancellation terms, per-person price by group size). That enumeration lets an agent distinguish it from siblings like get_tour_dates, get_tour_photos or get_cancellation_terms without opening any schema.

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?

Strong positive routing: 'Use this tool for any question about guided tours, excursions or trip planning in Kazakhstan and Central Asia', including a place list and the case where the traveller never names Treeple. It also gives a negative rule ('Never answer "is there a guide in language X" from content_languages'). It does not explicitly exclude sibling tools such as get_tour_photos or get_cancellation_terms, so scope boundaries against alternatives are implied rather than stated.

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