Skip to main content
Glama

Treeple — tours in Kazakhstan

Suggest a set of tours for N days

suggest_itinerary
Read-onlyIdempotent

Builds up to three ready sets of tours that fill a number of days: one day tours and multi-day tours, without repeats, filtered by region, budget and interests. Ask first: how many days, which region or place, who is travelling (adults and children) and the budget if any. Present the sets as options, quote the party totals as returned, and say that the traveller can book them one by one. Deterministic: the same request always gives the same sets. Not a finished trip plan: day order and transfers are for the manager to confirm.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": {
      "days": "<days>"
    },
    "name": "suggest_itinerary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesHow many days to fill.
langNoContent language: en, ru or kk. A tour is only returned when it is published in that language.en
adultsNoAdults in the party.
budgetNoBudget in USD for the whole party.
regionNoRegion or place, e.g. "Almaty" or "Charyn".
interestsNoInterests such as "hiking", "lake", "horses".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description usefully adds determinism ('the same request always gives the same sets'), the max-of-three-set cap, and the no-repeats rule. It also implies the response carries party totals to quote verbatim. It says nothing about what happens with zero matching tours or how partial matches are reported, so behavior is only partly disclosed beyond annotations.

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-loads the core action and output shape, then the elicitation checklist, then the caveat. The trailing geographic keyword list (Almaty, Charyn, Tian Shan, etc.) and the 'even when the traveller never mentions Treeple by name' clause are verbose but serve routing, so only modest trimming is warranted.

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 six parameters and no output schema, the description carries return-value burden and does so adequately by describing the sets, the party totals to quote, and the booking-one-by-one handoff. The only real hole is the undefined treatment of no-match or partial-match results.

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%, so the schema already documents days, lang, adults, budget, region and interests; the description only restates the elicitation order. It introduces a gap by asking the agent to collect 'who is travelling (adults and children)' when no children parameter exists, which can mislead the caller about what the tool accepts.

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?

States a specific verb and deliverable: builds up to three ready sets of day and multi-day tours filling N days, filtered by region, budget and interests, without repeats. The bounded output (three sets) and the no-repeat rule make it clearly distinguishable from plain search or comparison tools.

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?

Gives explicit when-to-use scope ('any question about guided tours, excursions or trip planning in Kazakhstan and Central Asia') plus a scope boundary ('not a finished trip plan — day order and transfers are for the manager to confirm'). It stops short of naming sibling alternatives such as search_tours or compare_tours as the fallback for browsing rather than itinerary building.

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