Skip to main content
Glama

Nosdeputes Fr List Votes

nosdeputes_fr_list_votes
Read-onlyIdempotent

Recorded votes (scrutins) of the French Assemblee nationale as published by the NosDeputes.fr civic-tech mirror, optionally narrowed to the votes cast by one deputy via deputy_slug, across the 16th (default), 15th, or 14th legislature. Returns the vote records NosDeputes holds for that chamber. Answers how the French Assembly, or a named French deputy, voted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25
    },
    "name": "nosdeputes_fr_list_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-100 (default 25)
deputy_slugNoFilter to votes cast by a specific deputy
legislatureNo

Output Schema

NameRequiredDescriptionDefault
votesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data is a civic-tech mirror rather than the official record, and results are limited to 'the vote records NosDeputes holds for that chamber' — an important coverage caveat for an openWorld source, plus the default legislature assumption (16th).

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 resource and source, then scope, then a one-line purpose statement. The middle sentence ('Returns the vote records NosDeputes holds for that chamber') largely restates the opening, which is mild padding for a three-parameter listing tool, but nothing else is wasted.

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?

With an output schema present, return-value details need not be spelled out. For a simple, non-destructive read tool with three parameters, the description covers provenance, coverage limits, legislature options, and the optional deputy filter — everything an agent needs to call it correctly.

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 67%, and the description compensates meaningfully for the weakest documented parameter: legislature is undocumented in the schema yet the description supplies the allowed values (16th default, 15th, 14th). deputy_slug is described in both places, while limit is left to the schema, so the added value is real but partial.

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 (recorded votes / scrutins of the French Assemblée nationale), states the source (NosDeputes.fr mirror), and distinguishes itself from siblings such as nosdeputes_fr_list_groups and nosdeputes_fr_search_questions by closing with 'Answers how the French Assembly, or a named French deputy, voted.' An agent can identify this as the parliamentary-vote listing tool without opening the 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?

It clearly establishes the use case (retrieving how the Assembly or a specific deputy voted) and describes the optional deputy_slug narrowing, which tells the agent when to filter rather than call bare. It stops short of explicit exclusions or naming an alternative for related needs (e.g., deputy profiles), so usage context is clear but not fully comparative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.