holidays
French metropolitan public holidays for 2026 or 2027 (C. trav. L.3133-1). Optional Alsace-Moselle extras. No live fetch. Paid $0.01 USDC Base x402.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
fr-legal-kit
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full transparency burden. It discloses that no live fetch occurs and that payment of $0.01 USDC is required, but omits auth, error behavior, and output shape.
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?
Extremely concise with key facts front-loaded: purpose, legal reference, options, and constraints. Every sentence adds distinct information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Minimal context: no output schema, no parameter documentation, and no explanation of how to select 2026 vs 2027 or the Alsace extras. For an agent to call correctly, more detail is needed.
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?
Input schema is empty and no parameters are documented, so the baseline is 4. The mention of optional Alsace-Moselle extras is ambiguous because no parameter is declared, but it does not contradict the empty 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?
Clearly identifies the tool as returning French public holidays for 2026 or 2027, with legal reference. It does not state an explicit verb like 'get' or 'list', but the resource and scope are unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Mentions 'no live fetch' and cost, but does not explain when to choose this tool over siblings like alsace_holidays or how to request the optional Alsace-Moselle extras. No alternative or conditional guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.7/5.0
Disambiguation3/5
Many tools cover adjacent legal concepts such as down payments (acompte/arrhes), payment deadlines (due_date/due_eom/days_late), and identifier checks (check_siret/siren_from_siret/vat_key/eori), which can cause misselection. The descriptions do distinguish them clearly, but the sheer volume of overlapping categories still creates boundary confusion for an agent.
Naming Consistency4/5
All tool names use lowercase snake_case and are mostly short, readable French legal nouns or noun phrases, so there is a predictable stylistic pattern. The mix of French and English names and the occasional verb-led names like check_siret or siren_from_siret prevent a perfect score.
Tool Count1/5
With 68 tools, this server is far beyond the well-scoped 3-15 tool range and even beyond the 50+ extreme-mismatch threshold. Each tool is a tiny one-purpose helper, but the set as a whole is overwhelming and should be grouped into fewer, broader tools or split into multiple servers.
Completeness5/5
The tool surface covers an impressively broad range of French legal needs: statutory invoice mentions, payment penalties, holidays, VAT calculations, identifier checks, warranties, withdrawal rights, and dunning steps. There are no obvious dead ends, and mention_fields acts as a completeness checklist for required invoice mentions.