Skip to main content
Glama

Suivi des programmes (ce qui a changé)

suivi_programmes
Read-onlyIdempotent

Chronologie des programmes : publication, nouvelles mesures annoncées (avec leur date) et mises à jour détectées par la vérification quotidienne. Pour répondre à « qu'est-ce qui a changé cette semaine ? », « quand X a-t-il publié ses mesures ? ». Filtrable par programme et par date.

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

Input Schema

NameRequiredDescriptionDefault
depuisNoDate de début AAAA-MM-JJ (optionnel)
limiteNoNombre maximum d'événements (défaut 30)
programmesNoLimiter à certains programmes (par défaut : tous)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / programmes / items / description
      Previous value: -"Identifiant du programme : attal = Gabriel Attal (Renaissance) ; lfi = Jean-Luc Mélenchon (La France insoumise) ; philippe = Édouard Philippe (Horizons) ; retailleau = Bruno Retailleau (Les Républicains)"New value: +"Identifiant du programme : attal = Gabriel Attal (Renaissance) ; lfi = Jean-Luc Mélenchon (La France insoumise) ; philippe = Édouard Philippe (Horizons) ; retailleau = Bruno Retailleau (Les Républicains) ; tondelier = Marine Tondelier (Les Écologistes)"
    • changedInput schema / properties / programmes / items / enum
      Previous value: -[
      -  "attal",
      -  "lfi",
      -  "philippe",
      -  "retailleau"
      -]New value: +[
      +  "attal",
      +  "lfi",
      +  "philippe",
      +  "retailleau",
      +  "tondelier"
      +]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is lower. The description does add real behavior: updates are surfaced via a daily verification pass and results come back as a dated chronology, which tells the agent about data freshness and ordering. It does not say which direction the chronology runs, how many events come back by default, or when the daily check last ran.

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?

Three short sentences, with the content inventory front-loaded before the example questions and the filter note. The example questions earn their place as retrieval cues, though the closing filter sentence partly duplicates what the schema already states.

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 read-only, fully described three-parameter tool with no output schema, the description covers what an event is, that events are dated, and how filtering works. Remaining gaps are minor: result ordering direction and the default event cap, both of which are either schema-documented or easy to infer.

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 all three parameters, including the enum with full candidate names, are already documented in the schema. The description only repeats 'filtrable par programme et par date' and never mentions the limite cap or the default of 30, so it adds little beyond structured data — baseline 3.

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 the resource (chronologie des programmes) and specifies exactly what events it contains: publications, newly announced measures with dates, and updates detected by daily verification. That separates it from the sibling tools that read measures or programs directly, though it never names those alternatives explicitly.

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

Usage Guidelines4/5

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

It gives concrete trigger questions — « qu'est-ce qui a changé cette semaine ? » and « quand X a-t-il publié ses mesures ? » — so an agent knows this is the tool for change-tracking and date-anchored questions. It stops short of saying when not to use it or which sibling to prefer for plain program listing or measure reading.

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.