Skip to main content
Glama

Ce qui a changé

changements
Read-onlyIdempotent

Ce qui a changé, du plus récent au plus ancien : nouvelles mesures, modifications, abandons, retraits, changements de statut, nouveaux candidats. Filtres facultatifs par candidat, thème, type et date de début.

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": "changements"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType de changement.
limitNoNombre maximal de résultats.
sinceNoDate de début incluse, au format AAAA-MM-JJ.
themeKeyNoClé du thème (voir « lister_themes »).
candidateIdNoIdentifiant du candidat (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful ordering semantics (most recent first) and the set of change categories returned. It stops short of disclosing result volume limits or pagination behavior, which matters for a feed tool.

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 compact sentences with the ordering and content scope front-loaded before the optional filters. No filler or repetition, though the category list is slightly long relative to the value it adds.

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 read-only feed with full schema coverage and no output schema, the definition covers purpose, ordering and filters adequately. It leaves gaps around what a change record contains and whether results are paginated, which an agent would want when composing a response.

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 is already documented in the schema. The description restates the filter dimensions but adds no semantics beyond the schema — it omits the limit parameter entirely and gives no hint about date format or enum values.

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 names a concrete resource — a change feed ordered from newest to oldest — and enumerates the kinds of entries it contains (nouvelles mesures, modifications, abandons, retraits, changements de statut, nouveaux candidats). An agent can tell this is a chronological changelog rather than a search tool. It does not explicitly distinguish itself from siblings such as actualites or rechercher_mesures, so it falls short of 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?

It states that filters by candidat, thème, type and date de début are optional, which implies the unfiltered feed is the default usage. However, it gives no guidance on when to prefer this tool over actualites or rechercher_mesures, and no exclusions or prerequisites are mentioned.

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