wemake.holiday

Travel route ideas

list_route_ideas

Read-only

Ready-made multi-stop travel routes (stations, nights, best months, highlights) that already exist on wemake.holiday — optionally filtered by country (ISO code) and topic. Nothing is generated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_route_ideas"
  }
}

Input Schema

Name	Required	Description
`limit`	No	how many (1-30), default 12
`topic`	No	optional topic keyword as used by wemake.holiday, e.g. wandern, kultur, strand
`country`	No	optional ISO country code, e.g. TH or IT
`language`	No	answer language, ISO code (default en)

Output Schema

Name	Required	Description	Default
`total`	Yes
`routes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and external-source behavior are covered. The description adds real value by stating the data pre-exists on wemake.holiday and that nothing is generated, but it says nothing about result ordering, pagination beyond the limit param, or caching/staleness.

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?

A single front-loaded sentence with a parenthetical field list, then the key differentiator ("Nothing is generated") placed at the end for emphasis. No filler.

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 a full output schema and complete annotation set, the description only needs to convey what the tool returns and its non-generative nature, both of which it does. The alternative-routing gap exists but is minor against structured fields that already carry the rest.

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 all four parameters are already documented with examples. The description only echoes the country/topic filters and adds no format or behavior detail beyond the schema, which is the expected baseline.

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 resource (ready-made multi-stop travel routes on wemake.holiday) and enumerates the returned fields (stations, nights, best months, highlights). The clause "Nothing is generated" cleanly separates it from generative siblings like plan_trip, though no sibling is named explicitly.

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 implied rather than stated: browse pre-existing routes, optionally narrowed by country and topic. It never says when to prefer this list over get_route_idea for a single route, nor when a generative planning tool would be the better call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All wemake.holiday tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?