Stayspan Schengen Days

Find Schengen reset dates

find_schengen_reset_dates

Read-onlyIdempotent

Use this when the user wants schengen days left to return, a schengen 90 day rule projection or a days in Europe calculator for future availability. Projects window headroom on the next 180 dates with a daily CSV, assuming no further stays and departure by the reference date. Up to 60 stays over 1,100 days, years 1900–2100. Reference date defaults to America/New_York today. Headroom is not maximum consecutive trip length. Does not model bilateral agreements, residence permits, long-stay visas or visa-sticker limits; not legal advice.

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": {
      "past_stays": "<past_stays>"
    },
    "name": "find_schengen_reset_dates"
  }
}

Input Schema

Name	Required	Description	Default
`past_stays`	Yes	Up to 60 short stays spanning at most 1,100 days. Example: [{"entry_date":"2026-03-05","exit_date":"2026-03-20"}]. Use [] for none. Exclude residence-permit and type D visa days.
`reference_date`	No	Projection starts the day after this date. Example: 2026-03-31 or March 31, 2026. If omitted, uses today's date in America/New_York and says so.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`note`	Yes
`notes`	Yes
`days_left`	Yes
`days_used`	Yes
`downloads`	Yes
`reset_dates`	Yes
`reference_date`	Yes
`reset_event_count`	Yes
`first_available_date`	Yes
`full_90_available_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical assumptions: no further stays, departure by the reference date, the 180-date projection window, up to 60 stays over 1,100 days, year range 1900–2100, default reference date in America/New_York, and the distinction between headroom and maximum consecutive trip length. It also lists what is not modeled, including bilateral agreements, residence permits, long-stay visas, and visa-sticker limits, plus a legal-advice disclaimer.

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?

The description is front-loaded with the primary use case and then layers assumptions, constraints, and exclusions efficiently. It is dense but every sentence earns its place; the only minor cost is that the dense clauses require careful reading.

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 an output schema present, the description need not explain return values. It provides the missing behavioral context an agent needs: projection scope, assumptions, input limits, default behavior, exclusions, and legal caveat. Nothing material is missing for correct invocation.

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 fully documents past_stays and reference_date. The description adds some useful constraints, such as the 1900–2100 year range and the no-further-stays assumption, but most parameter semantics are already covered by the schema.

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 a specific capability: projecting Schengen 90/180 window headroom over the next 180 dates with a daily CSV. It distinguishes itself from a simple day-count by clarifying that headroom is not maximum consecutive trip length, though it does not explicitly name its siblings calculate_schengen_days or plan_schengen_trip.

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?

It gives clear trigger phrases: 'when the user wants schengen days left to return, a schengen 90 day rule projection or a days in Europe calculator for future availability.' It also states key assumptions and exclusions, but does not explicitly route the agent to or away from the sibling tools.

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

All Stayspan Schengen Days 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?