Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

national_sections

Retrieve all 57 editorial categories from The National's Arc section taxonomy accepted by national_headlines, excluding podcasts, newsletters, puzzles, partner, and promotional surfaces.

Instructions

Get The National sections. Returns all 57 editorial categories in The National's Arc section sitemap taxonomy that are accepted by national_headlines. Podcast, newsletter, puzzle, partner and promotional surfaces are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well by disclosing the exact result count (57), the source taxonomy (Arc section sitemap), and the categories that are excluded. It does not cover authentication, rate limits, or error behavior, but for a zero-parameter read-only taxonomy endpoint the key behavioral traits are the scope and exclusions, which are clearly stated.

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?

The description is two sentences, front-loaded with the core action and then the precise scope and exclusions. Every clause earns its place, and there is no filler or repetition.

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?

Given the simplicity of the tool (no parameters, no annotations, no output schema), the description provides everything needed: the result set size, the taxonomy source, the acceptance constraint tied to national_headlines, and the excluded surfaces. No further output format explanation is required because the description effectively defines the returned category list.

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 no parameters, so the baseline score is 4. The description does not need to explain parameter usage, and it appropriately focuses on what the tool returns instead.

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 ('Get The National sections') and immediately qualifies it with the exact scope: all 57 editorial categories in The National's Arc section sitemap taxonomy accepted by national_headlines. It also distinguishes itself from adjacent content by naming excluded surfaces (podcast, newsletter, puzzle, partner, promotional), so an agent can identify the tool 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?

The description gives clear context for use: this returns the sections that national_headlines accepts, which implicitly tells an agent when this tool is needed. It also details what is out of scope via the exclusion list, but it does not explicitly name an alternative tool or state when not to use this one.

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