Skip to main content
Glama

Nosdeputes Fr

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Groups

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.

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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "abrev": {
+            "description": "Group acronym (e.g. RE, LFI-NUPES)",
+            "type": "string"
+          },
+          "couleur": {
+            "description": "Group color code",
+            "type": "string"
+          },
+          "id": {
+            "description": "Group identifier",
+            "type": "number"
+          },
+          "nom": {
+            "description": "Full group name",
+            "type": "string"
+          },
+          "nombre_deputes": {
+            "description": "Number of members",
+            "type": "number"
+          },
+          "slug": {
+            "description": "Group URL slug",
+            "type": "string"
+          },
+          "url_assemblee": {
+            "description": "Official Assemblée group URL",
+            "type": "string"
+          },
+          "url_nosdeputes": {
+            "description": "Full NosDéputés group URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior4/5

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

While the safety profile (readOnlyHint, idempotentHint) is handled by annotations, the description adds significant behavioral context by detailing the exact data fields returned (id, slug, acronym, etc.). This provides the agent with a clear understanding of the output structure and resource context.

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?

The description is highly efficient. It front-loads the core purpose and then immediately follows with usage caveats, adding no unnecessary fluff while remaining extremely comprehensive.

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?

Given the minimalist input schema, the description is perfectly complete. It covers the resource definition, data fields, default behavior, and valid parameter values, leaving nothing for the agent to assume.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate fully. It effectively explains that the 'legislature' parameter is not mandatory, provides the sensible default, and defines the valid ranges for historical lookups (e.g., 15 or 14).

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 is highly specific, identifying the resource (political groups of the French Assemblée nationale), the source (NosDéputés), and listing the specific data points returned (id, slug, name, etc.). This clearly distinguishes it from general grouping or listing tools.

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

Usage Guidelines5/5

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

The description provides explicit usage constraints for the primary input parameter. It clearly states the default behavior (16th legislature) and the specific alternatives acceptable (legislature 15 or 14), providing precise operational guidance.

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

All Nosdeputes Fr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources