Skip to main content
Glama

Méthodologie

methodologie
Read-onlyIdempotent

Texte intégral de la méthodologie de PresiTracker2027 : recensement, suivi des programmes, questionnaire, calcul des proximités et des groupes, sondages, parrainages, actualité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": "methodologie"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds one useful behavioral fact — "texte intégral" signals a full-document dump rather than a summary, implying a potentially large payload. It says nothing about output format, length, or whether the text is chunked, which leaves a real gap for a document-retrieval tool.

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?

One sentence, front-loaded with the resource identity, followed by a compact topic enumeration. No preamble, no restatement of the tool name, nothing to trim.

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 zero-parameter, read-only document fetch with no output schema, the description covers what is returned (the full methodology) and its subject areas. The only shortfall is that it does not warn about output size or structure, which matters for a full-text dump that an agent must budget context for.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero properties, so per the baseline this scores 4. Nothing in the description contradicts or complicates the no-argument contract, and the enumeration of covered sections helps the agent predict what the single call 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?

"Texte intégral de la méthodologie de PresiTracker2027" names a specific verb (retrieve full text) and a specific resource (the methodology document), which is clearly distinct from the data-oriented siblings like parrainages, sondages, or comparer_candidats. The enumerated topics (recensement, questionnaire, calcul des proximités, etc.) further pin down the content. It stops short of explicitly contrasting itself with a sibling, so it is a 4 rather than a 5.

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?

There is no explicit statement of when to call this tool versus the sibling data tools (e.g., "call this before interpreting proximity scores"). Usage is only implied by the topic list, from which an agent can infer this is the reference document for how the site computes groups and proximities. That is minimum-viable guidance, not routing guidance.

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