Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dw_sections

List the DW English-edition sections accepted by dw-headlines, grouped by regions, topics, and categories, with each section's slug, name, and URL. No parameters required.

Instructions

Get DW sections. Lists the DW English-edition sections accepted by dw-headlines, grouped under the site's three navigation groups: regions, topics and categories. Each entry has a stable slug, display name and the section url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that the result is a grouped listing and that each entry carries a stable slug, display name and url. It doesn't state read-only-ness explicitly or ordering guarantees, but for a zero-parameter listing the behavioral surface is nearly fully covered.

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?

Three front-loaded sentences, each carrying distinct information (what it returns, how it's grouped, entry fields, no params). Slightly redundant to state the no-parameter fact twice, but nothing is wasted.

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?

No output schema exists, yet the description documents the shape of each entry (slug, name, url) and the three top-level groups, which is what an agent needs to consume the result. Only minor gaps remain, such as ordering or whether urls are absolute.

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,' removing any doubt about calling it argument-free.

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 and resource ('Get DW sections') and immediately scopes it: English-edition sections accepted by dw-headlines, grouped into regions/topics/categories. This distinguishes it from the many other *_sections siblings by naming the consumer tool and the exact grouping.

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?

The phrase 'sections accepted by dw-headlines' tells an agent exactly why it would call this tool — to discover valid slugs before fetching headlines. It stops short of explicit when-not-to-use or naming alternative discovery paths, which keeps it at a 4 rather than 5.

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