Skip to main content
Glama

Recherche de mesures

rechercher_mesures
Read-onlyIdempotent

Recherche des mesures par mots-clés dans leur titre et leur détail (sans tenir compte des accents ni des majuscules), avec filtres facultatifs par thème, candidats et statut. Les résultats sont classés par candidat (ordre alphabétique), puis par thème : jamais par pertinence ni par popularité.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rechercher_mesures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximal de résultats.
queryNoMots-clés, tous requis (par exemple « retraite 62 ans »).
statusNoStatut de la mesure : « active » ou « abandonnee ».
themeKeyNoClé du thème (voir « lister_themes »).
candidateIdsNoIdentifiants des candidats (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description does add genuinely non-obvious behavior: accent/case folding and a fixed result ordering by candidate then theme, explicitly never by relevance or popularity. However it says nothing about result shape, pagination, or truncation behavior at the limit.

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?

Two sentences, no filler, with the matching semantics front-loaded before the filtering and ordering notes. The final clause about ranking is slightly emphatic but earns its place because the ordering is counterintuitive for a search tool.

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?

For a five-parameter, all-optional read tool with no output schema, the definition covers matching rules, optional filters and result ordering, which is the main thing an agent needs to interpret results. The remaining gap is that it does not describe what each result contains, which the absent output schema leaves undocumented.

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 every parameter including the theme enum and candidate ID pattern is already documented in the schema. The description only restates which filters exist and that they are optional, and points implicitly at lister_themes/lister_candidats for valid values, adding little beyond structured fields.

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?

States a specific verb and resource ('Recherche des mesures par mots-clés') and scopes the match to title and detail, with accent- and case-insensitive matching. It does not however distinguish itself from sibling tools such as mesures_candidat, which an agent might otherwise consider for candidate-scoped lookups.

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 clarifies that theme, candidate and status filters are all optional ('filtres facultatifs') and that keywords are conjunctive ('tous requis'), which implies the free-text-entry use case. It never states when to prefer this over the siblings mesures_candidat or lister_themes, and gives no exclusions.

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.

Resources