MCP Assemblée nationale

Scrutins Par Periode

scrutins_par_periode

Read-onlyIdempotent

Retrieve and filter French National Assembly roll-call votes within a 90-day date range by vote type and outcome, paginated newest first.

Instructions

Liste filtrée des scrutins entre deux dates (90 jours au plus).

À utiliser pour parcourir les scrutins d'une période : filtrer par type (ensemble d'un texte, article, amendement) et par résultat (adopté ou rejeté). 20 scrutins par page, du plus récent au plus ancien. Pour des chiffres agrégés, préférer tendances_scrutins.

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": {
      "date_debut": "<date_debut>",
      "date_fin": "<date_fin>"
    },
    "name": "scrutins_par_periode"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Numéro de page, à partir de 1.
`type`	No	Type de scrutin : `texte` (vote sur l'ensemble d'un texte), `article`, `amendement`, `autre` (motions, résolutions, suspensions de séance…) ou `tous`.	tous
`date_fin`	Yes	Date au format AAAA-MM-JJ.
`resultat`	No	Ne garder que les scrutins adoptés ou rejetés.	tous
`date_debut`	Yes	Date au format AAAA-MM-JJ.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds real behavioral detail beyond them: the 90-day window cap, 20 results per page, and newest-first ordering. It stops short of saying what happens when the range exceeds 90 days (error vs. truncation).

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?

Four tight sentences: purpose and constraint first, then usage, then pagination/ordering, then the alternative. Nothing is repeated and no sentence is expendable.

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?

For a paginated read-only list tool with rich annotations and a 100%-covered schema, the description supplies the remaining decision-relevant facts: the date-span limit, page size, sort order, and the aggregation alternative. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds interpretation the schema lacks: 20 scrutins per page reframes the `page` parameter, and 'du plus récent au plus ancien' explains what ordering the date parameters produce. The enum meanings themselves are left to the 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?

States a specific verb and resource ('Liste filtrée des scrutins') plus the hard scope constraint (between two dates, max 90 days). It also distinguishes itself from the sibling tendances_scrutins by naming it for aggregated figures, so an agent can route correctly without opening either schema.

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?

'À utiliser pour parcourir les scrutins d'une période' gives a clear use context, and 'Pour des chiffres agrégés, préférer tendances_scrutins' names an explicit alternative with the condition that selects it. It does not contrast against rechercher_scrutins, leaving that one routing decision to inference.

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