Skip to main content
Glama

Parrainages

parrainages
Read-onlyIdempotent

Suivi des 500 parrainages d'élus requis, candidat par candidat (ordre alphabétique) : décompte officiel du Conseil constitutionnel dès qu'il existe, sinon promesses annoncées par le candidat (non vérifiables). Les deux chiffres ne sont jamais mélangés.

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

Input Schema

NameRequiredDescriptionDefault
candidateIdNoIdentifiant du candidat (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds meaningful domain behavior: official counts take precedence when available, otherwise announced promises are shown, and the two figures are never mixed. It does not describe auth, rate limits, or response pagination, but the provenance caveat is substantive.

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?

Two dense sentences, front-loaded with the tracked resource and the official-versus-promised data rule. There is no filler or repetition.

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 one-parameter domain tool with no output schema, the description explains the two data sources and their non-mixing. It leaves the behavior when candidateId is omitted and the response structure unstated, which matters because no parameters are required.

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 coverage is 100%, and the parameter schema already documents candidateId and points to « lister_candidats ». The description adds alphabetical ordering and candidate-by-candidate scope, but does not clarify what omitting the optional candidateId returns.

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 specifically that the tool tracks the 500 required elected-official sponsorships, candidate by candidate in alphabetical order, and separates official Constitutional Council counts from candidate promises. The resource is clear, but no sibling alternative such as fiche_candidat is named for disambiguation.

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?

The description implies this is the tool for sponsorship tracking and specifies candidate-by-candidate/alphabetical scope. However, it gives no explicit when-to-use or when-not-to-use guidance and does not route the agent from or to sibling tools.

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