MCP Assemblée nationale

Declarations Groupes

declarations_groupes

Read-onlyIdempotent

Retrieve verbatim voting declarations published by parliamentary groups for a specific French National Assembly scrutin, using its UID; no analysis is added, so cite them as group statements.

Instructions

Déclarations publiques des groupes parlementaires sur un scrutin.

Reprend telles quelles les explications de vote publiées par les groupes (souvent aucune). Ne contient aucune analyse : à citer comme déclarations des groupes.

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": {
      "uid": "<uid>"
    },
    "name": "declarations_groupes"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	Identifiant du scrutin, par exemple « VTANR5L17V7324 » (obtenu avec rechercher_scrutins ou rechercher).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is lifted. The description still adds genuinely useful behavioral context: the content is often empty ('souvent aucune') and is verbatim with no analysis, which tells the agent to expect sparse or absent results and to avoid treating it as commentary.

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?

Two short sentences, front-loaded with the resource and scope, and the qualifier about verbatim content follows immediately. No filler.

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

Completeness4/5

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

For a one-parameter read tool with full annotations and no output schema, the description covers the main risk an agent faces (frequently empty results, verbatim not analytic). Only the absence of an explicit statement about return shape/pagination leaves a small gap, which is minor here.

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% and the single uid parameter is documented with an example and where to obtain it. The description adds nothing about the parameter, so baseline 3 applies.

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?

States a specific verb and resource ('Déclarations publiques des groupes parlementaires sur un scrutin') and clarifies it reproduces vote explanations verbatim with no analysis. That distinguishes it in kind from analytical siblings like positions_groupes, cohesion_groupes or tendances_scrutins, though no sibling is named explicitly.

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?

The closing instruction 'à citer comme déclarations des groupes' implies this is the citation-oriented source rather than the analytical one, so usage is implied. There is no explicit when-to-use / when-not-to-use statement or named alternative.

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