Skip to main content
Glama

fr_school_calendar

Retrieve French school holiday dates by school year and zone A/B/C, including académies, and test whether a specific date falls in a holiday period.

Instructions

French school holidays (calendrier scolaire, Éducation nationale) by school year and zone A/B/C (or overseas/Corsica), with académies, start/end dates, and an optional date test (is this date a school holiday, and where). Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD to test
yearNoSchool year e.g. 2026-2027
zoneNoA, B, C or overseas zone
academieNoAcadémie name filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well on the operational side: it discloses the x402 payment model, the exact price (0.001 USDC on Base per successful call), and that an unauthenticated call returns a 402 challenge instead of data. It does not cover output shape or the default behavior of an empty call, which is the remaining gap.

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 purpose is front-loaded in the first sentence, with cost and auth consequences trailing as secondary facts. The first sentence is dense with parentheticals, but each element (bilingual gloss, zone list, date test) contributes to correct selection, and the payment sentences earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Payment and authentication behavior are fully covered, and the description is adequate for selecting the tool. However, for a four-parameter, all-optional tool with no output schema and no annotations, it leaves the agent guessing about defaults (empty call, missing year) and the shape of the returned calendar, which are the details most likely to cause a mis-call.

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 all four parameters and the baseline is 3. The description adds only marginal meaning beyond it — expanding zone coverage to include Corsica and clarifying that `date` drives an is-this-a-holiday test — but says nothing about how `year` and `academie` interact or what an omitted `academie` filters to.

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 resource with its native-language gloss ("French school holidays (calendrier scolaire, Éducation nationale)"), the dimensions it is keyed by (school year, zone A/B/C, overseas/Corsica), and the auxiliary operation (date test). This is clearly distinguishable from the generic sibling `holidays` because it is explicitly scoped to French school calendars rather than public holidays.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: you call it with a year/zone for a calendar, or with a `date` to test whether that date is a holiday. It never says when to prefer this over the sibling `holidays`, nor what happens when no parameters are supplied, even though every parameter is optional.

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