Skip to main content
Glama

Mesures d'un candidat

mesures_candidat
Read-onlyIdempotent

Mesures détaillées d'un candidat, avec leurs sources et leur historique daté (ajout, modification avant / après, abandon, retrait). Filtrer par thème ou par identifiants de mesures : un programme complet est trop long pour une seule réponse.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "candidateId": "<candidateId>"
    },
    "name": "mesures_candidat"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeKeyNoClé du thème (voir « lister_themes »).
measureIdsNoIdentifiants des mesures (voir « fiche_candidat »).
candidateIdYesIdentifiant du candidat (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description does add real behavioural context beyond them, namely the shape of the returned history (ajout, modification avant/après, abandon, retrait) and an implicit warning about response size limits. It does not say what happens when filters are omitted (truncation? error? paging?), which is the main behavioural unknown.

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 sentences, both earning their place: the first defines the returned content, the second gives the filtering rule and the reason behind it. The purpose is front-loaded and there is no redundant restatement of the title or of the annotations.

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?

With no output schema the description must carry the return-value burden, and it does so by listing sources and the four history event types. The filtering rationale compensates for the absence of documented limits. The remaining gap is the unstated fallback behaviour when neither filter is supplied.

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%, so every parameter already carries its own description and even points to sibling tools for obtaining the theme key and IDs. The description reinforces the intended use of the filters but does not clarify whether themeKey and measureIds combine as AND or OR, nor how the enum keys map to themes. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific resource (detailed measures of a candidate) and enumerates the payload it carries: sources and a dated history of additions, before/after edits, abandonments and withdrawals. That is far more specific than the title alone. It does not, however, contrast itself with plausible siblings such as 'rechercher_mesures' or 'fiche_candidat', so sibling differentiation is left to the agent.

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 usage guidance: filter by theme or by measure identifiers, with the stated rationale that a full programme is too long for a single response. That tells an agent how to call the tool successfully in practice. It stops short of naming an alternative tool or stating when this tool should not be used instead.

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