Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Rechercher Deputes

rechercher_deputes
Read-onlyIdempotent

Find French National Assembly deputies by name, parliamentary group, department, or legislature and retrieve their uid for detailed lookup. Use department for 'Who is my deputy?' queries.

Instructions

Cherche des députés par nom, groupe, département ou législature (17e par défaut).

À utiliser pour retrouver l'identifiant (uid) d'un député avant d'appeler obtenir_depute. Les 14e, 15e et 16e législatures sont couvertes aussi. Sans nom, liste les députés (filtrables par groupe et par département). Pour « Qui est mon député ? », passez le département de la personne : la circonscription exacte dépend de l'adresse, ne la devinez pas. Pour une législature close, le groupe indiqué est le dernier du député dans cette législature.

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

Input Schema

NameRequiredDescriptionDefault
nomNoNom, prénom ou nom complet du député (accents et casse ignorés).
pageNoNuméro de page, à partir de 1.
groupeNoSigle du groupe, par exemple « RN ».
departementNoDépartement de la circonscription, en toutes lettres, par exemple « Gironde » ou « Côte-d'Or » (accents, tirets et casse ignorés). Pour une ville, indiquez son département.
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

A4.5/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 profile is covered. The description adds real behavior beyond them: default legislature 17, coverage of the 14th–16th, the listing mode when `nom` is absent, and the last-group caveat for closed legislatures. Only gaps are result ordering and volume.

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?

Front-loaded with the core action and the alternative-routing rule, and every sentence carries information. It is dense and multi-clause, but no sentence is 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?

All five optional parameters are covered and the two non-obvious cases (no-name listing, deputy-lookup) are resolved. With no output schema, return shape and pagination ordering are left implicit, which is a minor gap for a search tool.

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 and the schema already documents each parameter. The description still adds meaning the schema lacks: the department is the address-derived proxy for constituency and the group semantics differ for closed legislatures.

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 ("Cherche des députés") plus the searchable facets (nom, groupe, département, législature) and the default legislature. It also positions itself against the sibling obtenir_depute by framing itself as the uid-lookup step, so an agent can distinguish the two 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: use this to obtain the `uid` before calling obtenir_depute; with no `nom`, it degrades to a filtered listing. It also handles the ambiguous "Qui est mon député ?" case (pass the department, don't guess the constituency) and warns that for closed legislatures the group returned is the deputy's last one.

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