Stayspan Schengen Days

Calculate Schengen days

calculate_schengen_days

Read-onlyIdempotent

Use this when the user needs a schengen calculator, schengen days left, schengen overstay dates or a 90/180 rule calculator for past and planned short stays. Returns days used and left on the check date, stay compliance, overstay dates and daily CSV. Accepts ISO or English US text dates, up to 60 stays over 1,100 days, years 1900–2100. Open stays end at the check date; touching stays merge. Does not model bilateral agreements, residence permits, long-stay visas or visa-sticker limits; calculation aid, 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": {
      "stays": "<stays>",
      "check_date": "<check_date>"
    },
    "name": "calculate_schengen_days"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`check_date`	Yes	Window ends on this day, inclusive. Example: 2026-03-20 or March 20, 2026. Required for an ongoing stay.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`note`	Yes
`notes`	Yes
`days_left`	Yes
`days_used`	Yes
`downloads`	Yes
`check_date`	Yes
`window_end`	Yes
`stay_results`	Yes
`window_start`	Yes
`overstay_ranges`	Yes
`next_legal_entry`	Yes
`stay_result_count`	Yes
`overstay_day_count`	Yes
`first_overstay_date`	Yes
`next_entry_max_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses return contents (days used and left, stay compliance, overstay dates, daily CSV), date format support, stay/duration limits, handling of open stays and touching stays, and important exclusions. This gives an agent substantial operational context for correct invocation.

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?

The description is front-loaded with the trigger condition, then concisely covers outputs, input formats, edge-case behavior, and exclusions. Despite covering several constraints, every sentence contributes useful information without repetition.

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?

Given the presence of an output schema, the description does not need to detail return structure, yet it still summarizes key outputs. It also covers scope, constraints, edge cases, and legal caveats sufficiently for an agent to call the tool correctly.

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 description coverage is 100%, so parameter meanings are already well documented. The description still adds useful global semantics: ISO or English US text dates, up to 60 stays over 1,100 days, years 1900–2100, and that open stays end at the check date while touching stays merge.

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 purpose and use cases: "Use this when the user needs a schengen calculator, schengen days left, schengen overstay dates or a 90/180 rule calculator for past and planned short stays." It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tools find_schengen_reset_dates and 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?

The description provides a clear context for use with "Use this when the user needs..." and explicitly excludes certain domains such as bilateral agreements, residence permits, long-stay visas and visa-sticker limits. However, it does not name alternative tools or state when to use find_schengen_reset_dates or plan_schengen_trip instead.

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?