Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Suivre Sujet

suivre_sujet
Read-onlyIdempotent

Track a French National Assembly topic from 2012 onward, showing vote counts, outcomes, and majority group positions across legislatures.

Instructions

Suit un sujet d'une législature à l'autre, de 2012 (14e) à aujourd'hui (17e).

À utiliser pour « Depuis quand l'Assemblée vote-t-elle sur X ? », « Qu'a-t-on voté sur X sous chaque législature ? ». Donne, par législature, le nombre de scrutins dont le titre correspond, leur nature, adoptés et rejetés, et les derniers votes sur l'ensemble d'un texte avec leur uid et la position majoritaire de chaque groupe. Relevé factuel : un nombre de scrutins ne mesure pas l'importance d'un sujet.

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": {
      "sujet": "<sujet>"
    },
    "name": "suivre_sujet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sujetYesMots-clés du sujet, avec les accents français (« retraite », « mariage », « assurance chômage ») ; un pluriel est aussi cherché au singulier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered; the description earns credit by disclosing the shape of the result (counts per legislature, adopted vs rejected, latest votes with uid and each group's majority position). The closing caveat ("un nombre de scrutins ne mesure pas l'importance d'un sujet") usefully prohibits over-interpretation, though pagination/limits on the returned votes are not stated.

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 sentences, action and time range front-loaded, then output content, then a caveat — every sentence contributes and nothing is padded.

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

Completeness5/5

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

Single-parameter tool with no output schema, and the description fully compensates by describing what each result record contains plus an interpretive caveat. Nothing material is left for the agent to guess before calling it.

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 already documents accents, plurals and the 2–200 char bound, so the schema carries the load. The description adds only indirect meaning, framing `sujet` as free-form keywords tracked across legislatures; 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?

Specific verb and resource ("Suit un sujet d'une législature à l'autre") with an explicit temporal scope (2012/14e → 17e), and it enumerates what comes back per legislature (nombre de scrutins, nature, adoptés/rejetés, derniers votes avec uid et position majoritaire). It doesn't name a sibling such as rechercher_scrutins to sharpen the boundary, so it stops short of a 5.

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?

Two concrete example questions ("Depuis quand l'Assemblée vote-t-elle sur X ?", "Qu'a-t-on voté sur X sous chaque législature ?") make the intended use case obvious. There is no explicit when-not or named alternative, so the agent must infer the boundary against rechercher_scrutins and dossier_legislatif.

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