Skip to main content
Glama
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes

Obtenir Scrutin

obtenir_scrutin
Read-onlyIdempotent

Fetch official vote details: title, date, outcome, and for/against/abstention counts by parliamentary group using a vote ID.

Instructions

Détail d'un scrutin : titre, date, type, résultat officiel et décomptes.

Donne le nombre de pour, contre et abstentions, global puis par groupe parlementaire. Pour savoir comment un député ou un groupe a voté, utiliser ensuite votes_scrutin.

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": {
      "uid": "<uid>"
    },
    "name": "obtenir_scrutin"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesIdentifiant du scrutin, par exemple « VTANR5L17V7324 » (obtenu avec rechercher_scrutins ou rechercher).

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 readOnly/idempotent/non-destructive, so the bar is lower, and the description adds real value about content: official result plus for/against/abstention counts broken down globally and per parliamentary group. That is the kind of return-shape context annotations cannot convey, and no output schema exists to carry it.

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?

Two short sentences, front-loaded with what the tool returns and then the routing note. Every sentence earns its place with no 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?

With a single parameter at full schema coverage and no output schema, the description adequately covers both inputs (via schema) and outputs (via the enumeration of fields and counts). Only minor gaps remain, such as whether the group breakdown lists every group or just those that voted.

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 the uid parameter is fully documented in the schema, including example format and how to obtain it. The description adds nothing about the identifier, so the baseline 3 applies.

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?

The description names a specific resource (un scrutin) and enumerates exactly what is returned: titre, date, type, résultat officiel, décomptes. It also explicitly distinguishes itself from votes_scrutin, so an agent can tell the two apart 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 Guidelines4/5

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

The second sentence gives an explicit follow-up routing rule: to learn how a deputy or group voted, use votes_scrutin afterwards. It does not state the inverse exclusion (use rechercher_scrutins to find a uid), though the schema's uid description covers that path.

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