Skip to main content
Glama

Actualités

actualites
Read-onlyIdempotent

Titres récents d'un panel de médias de sensibilités différentes qui mentionnent un candidat ou la présidentielle : titre, média, date et lien vers l'article. Ordre chronologique, aucun média favorisé.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximal de résultats.
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?

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are in chronological order, the media panel spans differing editorial leanings, and no outlet is favored — a meaningful neutrality guarantee for a political-news tool. It does not discuss freshness window or whether results can be empty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the resource front-loaded and the returned fields appended as a compact list. No filler, though the two trailing clauses (chronological order, no favored outlet) could be tightened.

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 two-parameter read-only listing tool with no output schema, the description covers the resource, the return fields, the ordering and the neutrality guarantee — enough to call it correctly. Minor gaps remain around the default behavior when candidateId is omitted and result freshness, which for a news tool would matter.

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 the schema itself documents limit (1–50, default 20) and candidateId's format plus a pointer to lister_candidats. The description adds only the indirect hint that filtering by candidate is possible, without explaining the no-candidateId behavior or the ordering interaction with limit, so 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 (recent headlines) with a clear scope: a panel of outlets of differing sensibilities mentioning a candidate or the presidential election. It also enumerates the returned fields (titre, média, date, lien), so an agent knows exactly what it gets. It does not explicitly contrast itself with siblings such as changements or sondages, so it stops short of 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?

Usage is only implied: the phrase 'mentionnent un candidat ou la présidentielle' suggests the tool works both with and without candidateId, but neither condition is spelled out and no alternative tool is named. An agent can infer when to call it, but must guess at the boundary with media-adjacent siblings.

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