Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Exporter Scrutins

exporter_scrutins
Read-onlyIdempotent

Export lists of roll-call votes to CSV or JSON for raw-data analysis. Filter by date range (up to 90 days) or keywords to get spreadsheet- or script-ready data.

Instructions

Exporte une liste de scrutins en CSV ou JSON, pour analyser les données soi-même.

À utiliser quand on veut des données brutes (tableur, script) plutôt qu'un résumé. Indiquer soit date_debut et date_fin (90 jours au plus), soit sujet. Colonnes : uid, numero, date, legislature, type, contexte, resultat, titre, dossier_ref, dossier_libelle, url_civix. Les votes individuels s'exportent avec exporter_votes.

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

Input Schema

NameRequiredDescriptionDefault
sujetNoMots-clés, à la place des dates (100 scrutins au plus).
formatNoFormat de sortie : `csv` (avec en-tête) ou `json`.csv
date_finNoFin de période AAAA-MM-JJ.
date_debutNoDébut de période AAAA-MM-JJ (avec `date_fin`, 90 jours au plus).
max_lignesNoNombre maximal de lignes exportées.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words elsewhere: the 90-day window cap, the 100-scrutin cap when using `sujet`, and the exact column set returned. No output schema exists, so disclosing the columns is genuine added value.

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?

Front-loaded with verb, resource and formats, then usage criterion, then the parameter rule, then output shape, then the sibling pointer. The column enumeration is the only long element and it earns its place by substituting for a missing output schema.

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?

For a read-only export tool with no output schema, the description supplies both the constraints (period cap, row cap) and the returned columns, which is what an agent needs to decide whether to call it and how to use the result. Nothing material is 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 100%, so all five parameters are already documented, making 3 the baseline. The description does add one thing the schema cannot express — that `date_debut`/`date_fin` and `sujet` are mutually exclusive alternatives — but it repeats the 90-day limit already implied by the schema rather than adding new semantics.

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 ("Exporte une liste de scrutins") plus the two output formats, so the agent knows exactly what it gets. It also distinguishes itself from the closest sibling by noting that individual votes belong to exporter_votes, not this tool.

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?

"À utiliser quand on veut des données brutes (tableur, script) plutôt qu'un résumé" gives a clear selection criterion against summary-style siblings, and the either/or parameter rule is spelled out. It stops short of naming the specific alternative tool for summarized output, so the routing is implied rather than explicit.

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