Terudo partner

List plans

plans_list

Read-onlyIdempotent

Plans with their public price (price_cents, TTC). Give a destination for its plans, and days to also get daily plans sized for that stay. Without a destination: every fixed plan, for 'from' prices.

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": "plans_list"
  }
}

Input Schema

Name	Required	Description
`days`	No	Stay length, to build daily plans (1 to 30).
`context`	No	Optional: in one sentence, why you are calling this tool for the user. Helps Terudo improve these tools; never shown to anyone else.
`destination`	No	Destination code: ISO country code (MA, US, TR…) or a region code from destinations (EU-35…).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: prices are public and tax-inclusive (TTC), and the default no-destination call returns all fixed plans priced 'from' rather than any specific stay. It says nothing about result volume or pagination, which are the remaining unknowns.

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?

Three short sentences, front-loaded with what is returned and then the two input-driven modes; nothing is padded. The phrasing 'Give a destination for its plans' is slightly awkward and takes a re-read, but overall it is efficient.

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?

For a 3-parameter, all-optional, read-only tool with an output-shape hint (plans with price_cents, TTC) but no output schema, the description covers both call modes and the pricing semantics. What is missing is minor: no indication of how many plans come back or whether results are paginated.

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 the schema already documents days (1-30), destination (ISO code or region code) and context. The description reinforces the days/destination relationship (daily plans sized for the stay) and describes the no-destination default, but adds no syntax or format detail beyond the schema. 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 states what is returned (plans with their public price, price_cents, TTC) and distinguishes two operating modes: destination-filtered plans and, when 'days' is supplied, daily plans sized for the stay, versus the unfiltered 'every fixed plan, from prices' mode. The verb is implicit ('list' from the name/title) rather than stated, and no sibling tool is named, so it is clear but not fully differentiated.

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?

Usage context is explicit: supply a destination to get plans for that destination, add days to get daily plans sized for the stay, and omit destination to get all fixed plans with 'from' prices. This tells the agent how input choices change the call, but it names no alternatives (e.g. quote_trip or compatibility_check) and gives no exclusions.

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

All Terudo partner 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?