Skip to main content
Glama

Travel guide for a country or place

country_guide
Read-only

Short travel guide for a country, region or city (introduction, getting there, climate, safety …) from Wikivoyage, with a photo of the place. Always mention the source Wikivoyage and its licence CC BY-SA 4.0 with the source link.

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": {
      "place": "<place>"
    },
    "name": "country_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYescountry, region or city as its Wikivoyage article is called, e.g. Thailand, Tuscany, Lisbon
languageNoanswer language; de uses German Wikivoyage, all others English (default en)

Output Schema

NameRequiredDescriptionDefault
urlYes
guideYes
imageNo
introNo
sourceYes
licenseYes
sectionsNo
source_urlYes
history_urlNo
travel_warningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=true, openWorld=true, destructive=false, so safety is covered. The description adds genuinely useful context: the guide's sections (introduction, getting there, climate, safety), the inclusion of a photo, and a licensing obligation to credit Wikivoyage under CC BY-SA 4.0 with a source link. However, it says nothing about guide length limits, missing-article behavior, or how much content comes back.

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?

Two compact sentences with the resource and source front-loaded, followed by the attribution rule. The parenthetical section list is slightly open-ended but efficient. No filler.

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?

An output schema exists, so return values need not be explained, and the description still usefully characterizes the content and its licensing. Coverage of what happens when a place has no matching article, or of sizing limits, is the remaining gap for an open-world retrieval tool.

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 both parameters are already documented, including the language-to-Wikivoyage-edition mapping. The description adds only that the entity may be a country, region or city, which the schema already conveys. Baseline 3 is 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?

States a specific verb and resource: a short travel guide for a country, region or city, drawn from Wikivoyage, plus a photo. That is clearly distinguishable from hotel-, flight- and route-oriented siblings. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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: an agent can infer this is the tool for destination overviews rather than booking or routing. There is no explicit when-to-use statement, no exclusion such as 'do not use for hotel availability', and no prerequisites beyond the place naming convention.

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