Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

abcnews_sections

List the 8 core ABC News sections accepted by abcnews-headlines, including us, world, politics, business, technology, entertainment, health, and sports, with slug, name, and URL.

Instructions

Get ABC News sections. Lists the 8 core ABC News sections that abcnews-headlines accepts: us, world, politics, business, technology, entertainment, health and sports. Each entry has a slug, a display name and the section's page url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it discloses that the result is a fixed set of 8 sections and that each entry carries a `slug`, display `name` and page `url`. It leaves auth requirements, caching/stability and pagination unstated, but for a static enumeration tool those gaps are minor.

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?

Two tight sentences, no waste. The core purpose is front-loaded and the enumeration plus return-field detail follows only because it adds real value (it defines the accepted values of the sibling tool).

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?

For a zero-parameter, annotation-free tool with no output schema, the description supplies both the returned field shape and the reason the tool exists (feeding abcnews-headlines). Only marginal items such as whether the list is stable/complete are omitted.

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 baseline the schema cannot be improved on and there is nothing for the description to disambiguate. No penalty applies.

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 ABC News sections') and enumerates exactly what is returned: the 8 section slugs. It also explicitly links the output to the sibling `abcnews-headlines`, so an agent can distinguish this from abcnews_article/news/headlines 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 strongly implies usage by stating these are 'the 8 core ABC News sections that `abcnews-headlines` accepts', which tells the agent to call this to discover valid section values before calling abcnews-headlines. It stops short of an explicit 'use this before/when' instruction or a when-not-to-use clause, so it is clear context rather than full routing guidance.

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