Skip to main content
Glama

Fiche d'un candidat

fiche_candidat
Read-onlyIdempotent

Fiche d'un candidat : biographie, fonctions, parti, historique de statut sourcé, parrainages, et liste résumée de ses mesures (identifiant, thème, titre, statut, date de dernière modification). Le détail et l'historique des mesures s'obtiennent avec « mesures_candidat ».

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

Input Schema

NameRequiredDescriptionDefault
candidateIdYesIdentifiant du candidat (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 covered. The description adds genuinely useful behavior beyond that by describing the return shape, notably that measures are returned as a reduced list with specific fields (identifiant, thème, titre, statut, date de dernière modification) rather than full records. It says nothing about error behavior for an unknown candidateId, which is the remaining gap.

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, front-loaded with the resource name and its returned fields, then closing with the alternative tool. The parenthetical field list is dense but every item earns its place by telling the agent what it will and will not receive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of describing return values, and it does so field by field, including the deliberate truncation of measure data. For a single-parameter read tool with complete annotation coverage, nothing an agent needs to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema itself already points to « lister_candidats » for obtaining the identifier. The description adds no further meaning about the identifier's format or validity beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (a single candidate's profile) and enumerates exactly what it returns: biography, offices, party, sourced status history, endorsements, and a summarized measures list with the fields included. This is far more than a restatement of the title and lets an agent distinguish it from 'mesures_candidat' without opening the schema.

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 explicitly routes the agent away from this tool for measure detail and history, naming « mesures_candidat » as the alternative and stating the condition that selects it. The one gap is that 'parrainages' is both a field here and a sibling tool, and the description never clarifies that this tool returns only a summary while the dedicated tool gives the full record.

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