Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Rechercher Scrutins

rechercher_scrutins
Read-onlyIdempotent

Search French National Assembly roll-call votes by topic to retrieve each vote's date, official result, title, and uid for further lookup of details or individual voting records.

Instructions

Cherche des scrutins (votes de l'Assemblée nationale) par sujet.

À utiliser pour retrouver le vote d'un texte, d'un article ou d'un amendement. Renvoie pour chaque scrutin la date, le résultat officiel, le titre et son uid, à passer à obtenir_scrutin ou votes_scrutin. Un même texte donne souvent plusieurs scrutins (amendements, articles, vote sur l'ensemble).

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_scrutins"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNuméro de page, à partir de 1.
mots_clesNoMots-clés du sujet (« retraites », « assurance chômage », « budget 2026 »). Utiliser les accents français ; laisser vide pour lister les plus récents.
legislatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, open-world profile, so the description correctly spends its words elsewhere: it discloses the per-result payload (date, résultat officiel, titre, uid) and a genuinely useful behavioral caveat that one text often yields multiple scrutins (amendements, articles, vote sur l'ensemble). It omits pagination/volume behavior, which is the main remaining gap.

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 grouped into one paragraph: purpose first, usage second, output/handoff last. Every sentence carries information an agent needs and nothing is repeated from the schema.

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 no output schema, the description usefully enumerates the returned fields and the uid handoff, and warns that a single text maps to many scrutins. It is nearly complete; only result-set size/pagination expectations and the legislature scope are left implicit.

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 coverage is 67% and the schema itself explains each parameter well, including the hint to use French accents and to leave mots_cles empty for the most recent scrutins. The description only implies keyword ('par sujet') and never mentions the legislature or page parameters, so it adds little beyond the schema — baseline 3.

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 scrutins') and immediately glosses the domain term ('votes de l'Assemblée nationale'), removing ambiguity for an agent. It also separates itself from the retrieval siblings by framing itself as keyword search whose output feeds obtenir_scrutin.

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?

Explicitly says when to use it ('pour retrouver le vote d'un texte, d'un article ou d'un amendement') and names the two downstream tools it should hand off to. It does not state exclusions (e.g. when to prefer scrutins_par_periode or tendances_scrutins instead), so it stops short of a full when/when-not split.

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