Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reuters_sections

List Reuters top-level sections accepted by the section parameter, returning each section's slug, name, and landing-page URL. Use it to find valid section values before fetching content.

Instructions

List Reuters sections. Lists the top-level Reuters sections accepted by the section parameter of /reuters/section, returned under items. Each entry has a slug, a display name and the landing-page url. Takes no parameters.

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 burden. It discloses the key behavioral facts: no parameters are required, results are returned under `items`, and each entry carries slug/name/url. It does not explicitly assert read-only/no-side-effects, but for a listing endpoint it discloses more than the schema does.

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 purpose, then the linkage to the sibling, then the return shape. Every sentence adds information with no repetition of the name or filler.

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?

There is no output schema, so the description correctly compensates by naming the `items` container and the per-entry fields (slug, name, url). Combined with the no-parameter note and the sibling linkage, an agent has everything needed to call and consume it.

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?

Zero parameters, so the baseline is 4. The description reinforces this with 'Takes no parameters', which matches the empty schema and leaves no ambiguity for the agent.

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?

The description states a specific verb and resource ('List Reuters sections') and immediately clarifies scope ('top-level') while cross-referencing the sibling reuters_section via its `section` parameter. An agent can distinguish this discovery tool from reuters_section/reuters_articles without opening any schema.

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?

It clearly establishes the usage context by tying the output to the `section` parameter of `/reuters/section`, implying you call this to discover valid section values. It stops short of an explicit 'use this before calling reuters_section' instruction or a when-not-to-use statement, so it is clear context but not fully prescriptive.

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