Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Obtenir Depute

obtenir_depute
Read-onlyIdempotent

Retrieve a French National Assembly deputy’s profile, including parliamentary group, constituency, legislature and official links, by name or ID; ambiguous names return candidate matches.

Instructions

Fiche d'un député : groupe, circonscription, législature, liens officiels.

Indiquer uid ou nom (si le nom est ambigu, les candidats sont listés). La législature vaut 17 par défaut ; un ancien député (14e à 16e législature) est retrouvé automatiquement par son uid, dans sa législature la plus récente.

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

Input Schema

NameRequiredDescriptionDefault
nomNoNom du député, à la place de `uid` (accents et casse ignorés).
uidNoIdentifiant du député (PA…), à la place de `nom`.
legislatureNoLégislature : 17 par défaut ; les 14e, 15e et 16e sont aussi couvertes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior the annotations cannot: ambiguity produces a candidate list rather than a record, and a former deputy's uid is auto-resolved to the most recent legislature (14e–16e). It does not describe error behavior when neither uid nor nom is supplied, keeping it below a 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 no filler: content first, then identifier selection, then the default/legacy-legislature rule. Each sentence carries information an agent needs to construct the call correctly.

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?

With only three optional parameters and no output schema, the description adequately covers input selection and the key fallback rule, and the field list compensates for the missing output schema. The one residual gap is what the response looks like when the ambiguity branch triggers (candidate list shape), which is only gestured at.

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 is 3, but the description adds semantics absent from the schema: uid and nom are mutually alternative ('à la place de'), not cumulative, and the legislature default interacts with uid lookups for former deputies. That goes beyond restating the schema fields.

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+resource ('Fiche d'un député') and enumerates the content returned (groupe, circonscription, législature, liens officiels). It is clearly distinct from action-oriented siblings like bilan_depute or comparer_deputes, but it never names an alternative, so the differentiation is implicit rather than explicit.

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 description explains how to select the target ('Indiquer `uid` ou `nom`') and what happens when the name is ambiguous, which is genuine call guidance. However, it gives no explicit when-to-use vs. when-not guidance relative to rechercher_deputes (to find a uid) or bilan_depute (to get a voting record), leaving that selection to inference.

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