Skip to main content
Glama

Treeple — tours in Kazakhstan

Open one place, restaurant, article or tour category

get_content
Read-onlyIdempotent

Full entry for one item returned by search_content, addressed by its slug. For a place this also lists the tours that actually visit it — that list is curated, so an empty list means Treeple sells no tour there, not that none exists. For a tour category it lists example tours and how many tours the category holds. Fields absent from the response are absent from the catalogue: Treeple does not store restaurant coordinates or place ratings, and a missing field is never a zero. 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": {
      "type": "<type>",
      "slug": "<slug>"
    },
    "name": "get_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoContent language: en, ru or kk. A tour is only returned when it is published in that language.en
slugYesThe slug from a search_content result, e.g. "kolsai-lakes" or "trekking".
typeYesWhat kind of thing to look for. "locations" — places to see: lakes, canyons, mountains, city sights, national parks (use this for "what to see in Almaty"). "restaurants" — where to eat (use this for "where to eat near X"). "articles" — Treeple's own travel guides and background reading (use this for "articles about Charyn"). "tour_types" — the categories tours are sold in: trekking, jeep tour, food tour, photo tour and so on (use this for "what kinds of tours do you run").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world reads, and the description adds genuinely non-obvious semantics: the visiting-tour list is curated so an empty list means nothing is sold there, and an absent field means the catalogue does not store it rather than a zero value. That is exactly the kind of interpretation guidance an agent cannot get from annotations or schema, and it directly prevents false negative assertions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are dense and front-loaded with the highest-value semantics, but the closing sentence degenerates into a keyword-stuffed geography list (Almaty, Astana, Charyn, Kolsai, Altyn-Emel, Mangystau, Tian Shan) that inflates the description well beyond what an agent needs to route correctly.

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 explaining return values, and it does so adequately: it discloses per-type variations (visiting tours for places, example tours plus counts for categories) and the missing-field convention. The internal shape of a 'full entry' remains vague, but that is acceptable for a read tool whose annotations already cover the safety profile.

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 enum for type already spells out the four content kinds with use-case hints, so the description adds little per-parameter detail. Its only real addition is establishing that the slug must come from a search_content result, which is a useful provenance constraint but a small one against a fully documented schema.

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 opening sentence names a specific verb and resource -- the full entry for one catalogue item, addressed by slug, scoped to things previously returned by search_content. That cleanly separates it from the search sibling and from the tour-detail siblings, but it never states that a specific tour should be fetched with get_tour rather than this tool, leaving an ambiguity an agent must resolve from the enum.

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?

It gives explicit when-to-use triggers for the main cases: a place entry also shows visiting tours, a tour category shows example tours and counts, and it is the tool for general Kazakhstan/Central Asia trip questions. There is no explicit 'when not to use' or routing to get_tour / get_tour_dates for a named tour, so guidance is clear but incomplete on alternatives.

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