MCP Assemblée nationale

Fetch

fetch

Read-onlyIdempotent

Retrieve the full record for a National Assembly search result by ID, including vote details, deputy or group profiles, and dossier timelines with sourced French markdown.

Instructions

Récupère le contenu complet d'un résultat de search.

Un scrutin, un député, un groupe ou un dossier législatif (chronologie de ses scrutins). Renvoie un JSON {"id", "title", "text", "url", "metadata"} ; text est du markdown français avec décomptes, sources et liens.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Identifiant renvoyé par `search` : scrutin:<uid>, depute:<uid>, groupe:<sigle> ou dossier:<DLR…>.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is low. The description still adds meaningful content: it documents the exact return envelope (`id`, `title`, `text`, `url`, `metadata`) and that `text` is French markdown containing vote counts, sources, and links — valuable since there is no output schema.

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?

Three short sentences, front-loaded with the core action and the tie to `search`, followed by the entity list and return shape. Slightly dense line-breaking but no wasted prose.

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 no output schema and full schema coverage, the description covers purpose, source of the id, and return payload. The only real omission is routing guidance versus the overlapping `obtenir_*` siblings.

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 `id` field already documents the accepted prefixes (scrutin:<uid>, depute:<uid>, groupe:<sigle>, dossier:<DLR…>) with length bounds. The description adds no format or validation detail beyond that, so the 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: retrieves the full content of a result returned by `search`, and enumerates the entity kinds covered (scrutin, député, groupe, dossier). It distinguishes itself from `search` but not from detail-oriented siblings like `obtenir_scrutin`, `obtenir_depute`, `obtenir_groupe`, or `dossier_legislatif`, which appear to overlap.

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 phrase "d'un résultat de `search`" implies this is a follow-up call to a search and that `id` comes from there, which is useful implicit guidance. However, it never says when to prefer this over `obtenir_scrutin`/`obtenir_depute`/`dossier_legislatif`, nor what happens if the id is stale or unknown — the alternatives among 26 siblings remain unresolvable from this text.

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