Skip to main content
Glama

Nosdeputes Fr Search Questions

nosdeputes_fr_search_questions
Read-onlyIdempotent

Search written or oral questions submitted by French Assemblée nationale deputies, filtered by free-text query, deputy slug, and question type (ecrite, orale, au gouvernement). Returns question title, deputy, date, and type.

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": {
      "query": "fiscalité"
    },
    "name": "nosdeputes_fr_search_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoecrite | orale | au gouvernement
limitNo
queryNo
deputy_slugNo
legislatureNo

Output Schema

NameRequiredDescriptionDefault
questionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a return-field summary (title, deputy, date, type), but that overlaps with the output schema and it says nothing about result ordering, pagination via limit, or legislature scoping.

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?

A single front-loaded sentence that states scope, filters, and returns with no filler. The only waste is the return-value clause, which duplicates what the output schema already provides.

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?

Output schema and annotations carry much of the burden, so the description need not explain returns or safety. However, for a five-parameter search tool it omits the meaning and defaults of limit and legislature, which 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.

Parameters3/5

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

With schema description coverage at 20% (only the type parameter is documented in-schema), the description compensates by naming three of the five parameters and giving the enum values for question type. It leaves limit and legislature entirely unexplained in both places, so the gap is only partly filled.

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 opens with a specific verb and resource ("Search written or oral questions submitted by French Assemblée nationale deputies") and names the narrowing filters, which is far more than the tautological title. It does not explicitly contrast with nearby siblings such as suggest_questions or search_interventions, so a 4 rather than a 5.

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?

Usage is only implied: the mention of free-text query, deputy slug, and question type suggests the ways to search, but there is no statement of when to prefer this tool over alternatives or when not to use it. An agent can infer the basic call shape but gets no 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.