mister-parc-mcp

État du parc

parc_etat

Read-onlyIdempotent

Get a fleet's status in one call: key figures, socle version, to-do section summaries, and changes since today's snapshot before drilling into details.

Instructions

L'état du parc en une réponse : chiffres clés du dernier relevé, version du socle, rubriques « À faire » (sans leur détail) et ce qui a bougé depuis la photo du jour.

À appeler en premier. genere date le relevé : il passe au mieux toutes les heures. Le détail d'une rubrique s'obtient par a_faire.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`page`	Yes
`socle`	Yes
`genere`	Yes	Date du relevé qui fonde la réponse (ISO 8601).
`a_faire`	Yes
`chiffres`	Yes	Les chiffres clés du relevé. Une clé que le relevé n'a pas mesurée est absente.
`changements`	Yes	Ce qui a bougé depuis la photo du jour.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavioral context the annotations cannot: the `genere` field dates the snapshot and it refreshes at most hourly, which tells the agent how stale the data may be. It stops short of describing failure modes or what openWorld implies here, so not a full 5.

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?

Three short sentences with zero filler: the payload is front-loaded, then the call-ordering instruction, then the freshness caveat and drill-down pointer. Every sentence carries distinct information.

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?

Output schema exists, so return values need not be spelled out, yet the description still summarizes what comes back and explicitly flags that 'À faire' items arrive without detail. Combined with the freshness note and the routing to a_faire, an agent has everything needed to call this correctly first in a session.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is nothing for the description to disambiguate. The mention of `genere` is a response field, not an input, and is covered by the existing output schema.

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?

The description states a specific resource and enumerates its contents: key figures from the latest snapshot, socle version, the 'À faire' sections without detail, and what changed since today's snapshot. It also implicitly separates itself from parc_a_faire by noting the sections come without their detail. An agent can distinguish it from the many parc_* siblings without opening a 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?

'À appeler en premier' gives an explicit ordering instruction relative to all siblings, and 'Le détail d'une rubrique s'obtient par `a_faire`' names the alternative tool and the condition that selects it. Both when-to-use and when-to-use-something-else are covered.

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