Skip to main content
Glama

Comparaison de candidats

comparer_candidats
Read-onlyIdempotent

Compare 2 à 6 candidats sur un thème : leurs mesures du thème, leurs positions sourcées sur les affirmations du questionnaire de ce thème (de −2, pas du tout d'accord, à +2, tout à fait d'accord) et leur taux d'accord calculé sur l'ensemble du questionnaire. Les candidats sont rendus dans l'ordre alphabétique, quel que soit l'ordre demandé.

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": {
      "candidateIds": "<candidateIds>",
      "themeKey": "<themeKey>"
    },
    "name": "comparer_candidats"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeKeyYesClé du thème (voir « lister_themes »).
candidateIdsYesIdentifiants des candidats (voir « lister_candidats »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description's added value is the return-ordering rule — results come back alphabetically regardless of the order requested — plus the −2..+2 position scale and the fact that the agreement rate is computed over the whole questionnaire, not just the theme. What is missing is any note on error handling for invalid theme keys or candidate IDs.

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, zero filler: the first defines the operation and the exact outputs, the second front-loads a non-obvious behavioral detail (alphabetical ordering overrides requested order). Every clause carries information an agent would otherwise have to guess.

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 present, the description carries the burden of describing returns, and it does so concretely: theme measures, sourced statement positions with their scale, and an agreement rate, plus the ordering rule. It is essentially complete for a two-parameter read tool, with only failure behavior on bad keys left unaddressed.

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%, and both parameters already carry descriptions that point to lister_themes and lister_candidats, with the enum and the 2–6 cardinality enforced in the schema. The description restates the 2-to-6 bound but adds no format, ordering, or edge-case semantics beyond what the input schema already states, so the baseline 3 applies.

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 opens with a precise verb and resource ('Compare 2 à 6 candidats sur un thème') and then enumerates exactly what is returned: theme measures, sourced positions per questionnaire statement, and an overall agreement rate. The plural, multi-candidate scope implicitly separates it from single-candidate siblings like fiche_candidat or mesures_candidat, but no sibling is named explicitly.

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?

Usage is only implied: the 2–6 candidate and theme-scoping constraints suggest 'use this when comparing several candidates on one theme.' There is no statement of when to prefer this over fiche_candidat or mesures_candidat, and no prerequisites or exclusions are given.

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