Skip to main content
Glama

Nosdeputes Fr List Groups

nosdeputes_fr_list_groups
Read-onlyIdempotent

Political groups (groupes parlementaires) of the French Assemblée nationale from NosDéputés: id, slug, name, acronym, colour, seat order and NosDéputés URLs for each group. Defaults to the 16th legislature (2022-2024); pass legislature 15 or 14 for earlier ones.

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": {
      "legislature": "14"
    },
    "name": "nosdeputes_fr_list_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
legislatureNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of groups returned.
itemsYes
sourceNoUpstream NosDéputés URL the list was read from.
legislatureNoLegislature the groups belong to (16 default, 15, 14).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered externally. The description adds the default legislature scope, which is behavior not captured in the schema, but says nothing about coverage completeness, upstream rate limits, or freshness of the data.

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 dense sentences with zero filler: the first defines the resource and return fields, the second front-loads the parameter default and allowed alternatives. Nothing repeats the name or annotation data wastefully.

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 an output schema present, the description needn't document return values, and the single optional parameter is explained, including its default. A small gap remains — no mention of whether all groups are returned in one response or whether the dataset only spans legislatures 14-16.

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 0% for the single 'legislature' parameter, so the description must carry the meaning — and it does, explaining that it defaults to the 16th legislature (2022-2024) and accepts 15 or 14 for earlier assemblies. It could have been more explicit that the value is a string numeral, but the semantic load is largely covered.

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?

The description names the exact resource (political groups / groupes parlementaires of the French Assemblée nationale) and enumerates the fields returned (id, slug, name, acronym, colour, seat order, URLs). It is clearly a listing tool for legislative groups, distinguishable from siblings like list_deputies or nosdeputes_fr_list_votes, though the verb 'list' is only implied by the tool name rather than stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives concrete guidance on the one meaningful choice: defaults to the 16th legislature (2022-2024), pass 15 or 14 for earlier ones. That is real usage guidance for the parameter, but there is no explicit when-to-use/when-not framing or named alternatives, so it stops short of routing guidance.

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.