Skip to main content
Glama
Sign In
MCP Assemblée nationale

MCP Assemblée nationale

by Toumi-Elyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Rechercher

rechercher
Read-onlyIdempotent

Search French National Assembly data by keyword to find votes, deputies, groups, or bills when the target type is unknown. Returns identifiers for use in other tools.

Instructions

Recherche globale dans les données de l'Assemblée nationale (CIVIX).

À utiliser quand on ne sait pas encore si l'on cherche un scrutin, un député, un groupe ou un dossier législatif. Renvoie jusqu'à 8 résultats par catégorie avec leurs identifiants, à réutiliser dans les autres outils. Pour un sujet de vote précis, préférer rechercher_scrutins ; pour une personne, rechercher_deputes.

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": {
      "requete": "<requete>"
    },
    "name": "rechercher"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNuméro de page, à partir de 1.
requeteYesMots-clés : sujet d'un vote, nom de député ou de groupe, titre d'un texte. Utiliser les accents français.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by saying it returns up to 8 results per category with identifiers meant to be reused in other tools, though it does not describe pagination behavior.

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 front-loaded with the core purpose and then moves efficiently through usage context, return behavior, and sibling alternatives. Every sentence adds actionable information 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 no output schema, the description helpfully states that results are capped at 8 per category and include identifiers for reuse. It covers the essential calling context for a broad search tool, though it could say more about pagination or result grouping.

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%, so the input schema already documents both requete and page thoroughly, including French accent guidance for requete. The description reinforces that requete is used across categories but does not add parameter syntax or constraints beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource: a global search over Assemblée nationale data (CIVIX). It also distinguishes itself from focused siblings by explaining that it is for cases where the category is not yet known, naming rechercher_scrutins and rechercher_deputes as alternatives.

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?

It gives an explicit use case: use when you do not yet know whether you are looking for a scrutin, député, groupe, or dossier législatif. It also gives concrete when-not guidance by directing precise vote searches to rechercher_scrutins and person searches to rechercher_deputes.

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

Deploy Server

Other Tools