Fetch France 24 English-edition top stories as structured JSON with title, URL, summary, publication time, and author.
Get France 24 top stories. Returns the current France 24 English-edition top stories. Each item has its title, URL, summary, publication time and author. Takes no parameters; use france24-headlines for a single region or topic.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden and discloses the return fields (title, URL, summary, publication time, author) and that no parameters are required. It could say more about read-only safety or freshness guarantees, but for a simple public news feed the disclosure is strong.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with zero waste: purpose first, return shape second, parameter/alternative note third. It is front-loaded and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a parameterless tool with no output schema, the description fully covers what the tool returns (fields listed) and when to use a sibling instead. No critical information is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so baseline is 4. The description reinforces this with 'Takes no parameters,' leaving no ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Get France 24 top stories') and immediately clarifies the edition and scope ('English-edition top stories'). It distinguishes itself from the sibling `france24-headlines` by describing that tool as the one for a single region or topic.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says 'Takes no parameters' and directs the agent to use `france24-headlines` when a single region or topic is needed. This gives a clear when-to-use and when-not-to-use rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.