Nosdeputes Fr

Get Deputy

get_deputy

Read-onlyIdempotent

Deputy profile by slug or numeric id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug_or_id`	Yes	NosDéputés slug or numeric id
`legislature`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Deputy numeric identifier
`nom`	No	Last name
`sexe`	No	Gender (M/F)
`slug`	No	NosDéputés URL slug
`email`	No	Contact email
`groupe`	No	Political group acronym
`prenom`	No	First name
`twitter`	No	Twitter handle
`photo_url`	No	Deputy photo URL
`nb_mandats`	No	Number of terms served
`profession`	No	Professional background
`departement`	No	Département code
`url_assemblee`	No	Official Assemblée website URL
`date_naissance`	No	Birth date (YYYY-MM-DD)
`url_nosdeputes`	No	Full NosDéputés profile URL
`circonscription`	No	Constituency number
`date_fin_mandat`	No	Term end date
`place_hemicycle`	No	Hemicycle seat position
`date_debut_mandat`	No	Term start date

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 1, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "slug_or_id": "jean-paul-dupont"
-  },
-  {
-    "legislature": "16",
-    "slug_or_id": "12345"
-  }
-]New value: +[
+  {
+    "slug_or_id": "thibault-bazin"
+  },
+  {
+    "legislature": "16",
+    "slug_or_id": "1"
+  }
+]

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "slug_or_id": "jean-paul-dupont"
+  },
+  {
+    "legislature": "16",
+    "slug_or_id": "12345"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "circonscription": {
+      "description": "Constituency number",
+      "type": "number"
+    },
+    "date_debut_mandat": {
+      "description": "Term start date",
+      "type": "string"
+    },
+    "date_fin_mandat": {
+      "description": "Term end date",
+      "type": "string"
+    },
+    "date_naissance": {
+      "description": "Birth date (YYYY-MM-DD)",
+      "type": "string"
+    },
+    "departement": {
+      "description": "Département code",
+      "type": "string"
+    },
+    "email": {
+      "description": "Contact email",
+      "type": "string"
+    },
+    "groupe": {
+      "description": "Political group acronym",
+      "type": "string"
+    },
+    "id": {
+      "description": "Deputy numeric identifier",
+      "type": "number"
+    },
+    "nb_mandats": {
+      "description": "Number of terms served",
+      "type": "number"
+    },
+    "nom": {
+      "description": "Last name",
+      "type": "string"
+    },
+    "photo_url": {
+      "description": "Deputy photo URL",
+      "type": "string"
+    },
+    "place_hemicycle": {
+      "description": "Hemicycle seat position",
+      "type": "string"
+    },
+    "prenom": {
+      "description": "First name",
+      "type": "string"
+    },
+    "profession": {
+      "description": "Professional background",
+      "type": "string"
+    },
+    "sexe": {
+      "description": "Gender (M/F)",
+      "type": "string"
+    },
+    "slug": {
+      "description": "NosDéputés URL slug",
+      "type": "string"
+    },
+    "twitter": {
+      "description": "Twitter handle",
+      "type": "string"
+    },
+    "url_assemblee": {
+      "description": "Official Assemblée website URL",
+      "type": "string"
+    },
+    "url_nosdeputes": {
+      "description": "Full NosDéputés profile URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description does not need to repeat safety traits. It adds minimal behavioral context beyond the schema, such as implying a single profile fetch, but lacks details like return format or error handling. This is adequate given the annotations.

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?

The description is extremely concise at one sentence, front-loading the essential purpose. It earns its place without fluff, though it could benefit from a brief note on usage scope without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with an output schema and rich annotations, the description covers the core purpose and primary parameter. However, it omits the meaning of 'legislature' and provides no guidance on when to choose this over sibling tools, leaving a moderate gap in context completeness.

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

Parameters2/5

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

Schema description coverage is only 50% (slug_or_id is described, legislature is not). The description repeats the slug_or_id semantics ('by slug or numeric id') but adds nothing for the legislature parameter, failing to compensate for the missing schema description. It provides no extra meaning beyond the existing parameter description.

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 'Deputy profile by slug or numeric id' clearly identifies the resource (deputy) and the lookup mechanism (slug or id), distinguishing it from list-type tools like list_deputies. It is concise and specific, matching the high standard of stating what the tool does.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as list_deputies, entity_profile, or resolve_entity. There are no explicit or implicit usage contexts, leaving the agent to infer from the name alone.

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

All Nosdeputes Fr tools Inspect

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.