madeira.fun Hiking Permits

Check Trail Availability

check_trail_availability

Read-onlyIdempotent

Day-by-day permit availability for one trail, from today up to 119 days ahead (Madeira dates). Each day is open (start times left for visitors), full (sold out for visitors), started (today only: every start time has already begun, nothing is left to book today; not sold out), closed, no_times (no start times listed) or unknown (not checked yet), with permits left for visitors and when it was last checked. Use date for one day, or from and to for a range; the default is the next 7 days. For the start times of a day, use get_start_times.

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": {
      "trail": "<trail>"
    },
    "name": "check_trail_availability"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day of a range (YYYY-MM-DD, a Madeira calendar date).
`date`	No	One day (YYYY-MM-DD, a Madeira calendar date).
`from`	No	First day of a range (YYYY-MM-DD, a Madeira calendar date).
`trail`	Yes	The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it defines every status value (open, full, started, closed, no_times, unknown), explains the non-obvious 'started' case (today only, not sold out), and lists the returned fields (permits left for visitors, last checked). That is exactly the context an agent needs to interpret results correctly.

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?

Front-loaded with the core capability, then scope, then status semantics, then routing to the sibling — a sensible order with no filler sentences. The status enumeration is dense but each term carries distinct decision value, so the length is justified rather than padded.

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 no output schema, the description takes on the burden of explaining return values and does so: per-day status, permits remaining, and last-checked time. Combined with annotations and full schema coverage, an agent has everything needed to call and interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each date parameter and the trail identifier (seo_slug, code, or name, accents ignored). The description adds real meaning by specifying the default range when neither date nor from/to is supplied, which the schema does not state.

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: day-by-day permit availability for one trail, bounded to a 119-day horizon. It explicitly separates itself from get_start_times, so an agent can distinguish it from the sibling that returns per-day start times without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete selection rules: use date for a single day, from and to for a range, default is the next 7 days. It also names the alternative tool (get_start_times) and the condition that selects it, which is the strongest possible routing guidance.

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

All madeira.fun Hiking Permits 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?