Skip to main content
Glama

Search English Wikivoyage travel guide articles: title

travel_wikivoyage_articles
Read-only

Search English Wikivoyage travel guide articles: title, short snippet with HTML removed, word count, last-edit page id and article URL, plus the total hit count. Snippets are search excerpts, not full guides; content is CC BY-SA. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "travel_wikivoyage_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, 2 to 100 characters
limitNoMax results, 1 to 20 (default 5)

Output Schema

NameRequiredDescriptionDefault
qNo
countNo
sourceNo
resultsNo
checkedAtNo
totalHitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare read-only and open-world; the description adds genuinely non-obvious behavior: a $0.002 per-successful-call charge, payment via x402 in USDC on Base/Solana and other networks, and the fact that failed calls are not billed. It also discloses the CC BY-SA licensing constraint, which matters for reuse. The remaining gap is that nothing is said about rate limits, result ordering, or pagination.

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?

Two sentences, front-loaded with the verb and resource, followed by pricing and licensing caveats that an agent genuinely needs before calling a paid endpoint. No boilerplate or repetition.

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 the field enumeration is partly redundant, but the description covers the two things an agent cannot infer from structured data: the cost/payment model and the excerpt-vs-full-guide limitation. Minor omissions around result ordering and failure modes keep it short of 5.

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%, so both `q` (2–100 chars) and `limit` (1–20, default 5) are already fully documented in the schema. The description adds no format, syntax, or query-operator guidance beyond that, so the 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 verb and resource ("Search English Wikivoyage travel guide articles") and enumerates the returned fields, so an agent can tell exactly what it gets. It does not differentiate from any sibling, but the sibling list contains no other Wikivoyage/content-search tool, so the ambiguity is low.

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?

"Snippets are search excerpts, not full guides" implies a boundary: use this for discovery, not for reading full article content. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative for retrieving full guide text.

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