Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

france24_sections

Lists the 12 France 24 English-edition sections accepted by france24-headlines, with slug, name, and URL for regions, topics, live-news, and TV shows.

Instructions

Get France 24 sections. Lists the 12 France 24 English-edition sections accepted by france24-headlines: six regions, four topics, the live-news wire-briefs hub and the tv-shows programmes hub. Each entry has the slug, display name and section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full load, and it does reasonably well for a read-only catalog: it discloses the exact count (12), the category breakdown, and the return shape (slug, name, url). It does not state that the list is static/English-only in a way that matters, but the 'English-edition' qualifier does bound it.

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?

Three tight sentences, front-loaded with the action, then the enumeration, then the return fields. No filler and no repetition of the tool name as prose.

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 and no parameters, the description correctly compensates by naming the three returned fields and the fixed size of the result set. An agent has everything needed to call it and consume the result.

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 tool takes zero parameters, so per the rubric baseline is 4. The description adds nothing to compensate for a missing schema, but nothing is needed.

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?

States a specific verb+resource ('Get France 24 sections') and immediately disambiguates from sibling tooling by naming `france24-headlines` as the consumer of these values. The enumeration of the 12 sections (six regions, four topics, two hubs) makes the scope unambiguous.

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?

Clearly implies when to use it: to discover section slugs that `france24-headlines` accepts. The linkage to the sibling is explicit, though it never says outright 'call this first to obtain valid `section` values' or what happens with an invalid slug.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools