C'est Chaud à Paris

France eSIM data plans

esim_plans

Read-onlyIdempotent

Returns prepaid eSIM data plans that work in France, for a given amount of data and trip length. Each plan carries its price with the date that price was checked, and a booking link. Relevant when a reader is travelling to Paris from outside the EU and needs mobile data on arrival.

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

Input Schema

Name	Required	Description
`gb`	No	Gigabytes wanted. Snaps to the nearest of 1, 3, 5, 10, 20, 50; omit for 10. Use `unlimited` instead for an unmetered plan.
`days`	No	How many days the trip lasts. Snaps to the nearest of 7, 15, 30; omit for 15.
`locale`	No	Language for the disclosure wording.
`unlimited`	No	Ask for unmetered plans instead of a size.

Output Schema

Name	Required	Description
`url`	Yes	The page a reader can open to do this themselves.
`items`	Yes	Matching plans, best match first.
`total`	Yes	How many plans are in `items`.
`country`	Yes	ISO 3166-1 alpha-2. Always FR — this is a Paris guide.
`requested`	Yes	What was actually asked of the catalogue, after snapping.
`approximate`	Yes	True when nothing matched the requested combination and these are the nearest plans instead. Say so when relaying them.
`attribution`	Yes	Who to credit and under what licence. The ODbL datasets behind most of this data require attribution wherever the data is used, including inside an answer you generate.
`unavailable`	Yes	True when the plan source could not be reached, or returned only prices too old to publish. An empty `items` with this false means there genuinely are none.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.2/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 handled. The description adds real value beyond that by disclosing what each result carries (price, the date that price was checked, a booking link), which signals that prices are point-in-time snapshots and points the agent at the booking action.

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, no filler: the first gives the output and its scoping inputs, the second gives the selection context. Front-loaded with the resource rather than a wind-up clause.

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 shape needn't be spelled out, and annotations cover the safety profile; the description fills the remaining gaps of purpose, provenance of price data and trigger context. The only residual looseness is the Paris-vs-France framing and the absence of any note about plan validity or coverage limits within France.

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%, with snapping rules, defaults and the `unlimited` alternative all documented inline, so the schema does the heavy lifting. The description only echoes two of the four parameters ('amount of data and trip length') and says nothing about `locale` or `unlimited` that the schema does not already state. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns prepaid eSIM data plans') plus the geographic scope ('work in France') and the two dimensions that determine results (data amount, trip length). No sibling tool covers eSIM or plans at all, so the agent can place it immediately without comparison.

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?

Gives a concrete usage condition: 'when a reader is travelling to Paris from outside the EU and needs mobile data on arrival.' This tells the agent both the scenario and the audience constraint (non-EU traveller). It stops short of exclusions, e.g. nothing tells the agent what to do for an EU resident with included roaming, and the guidance narrows to Paris while the tool covers all of France.

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

All C'est Chaud à Paris 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?