Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

abcau_sections

List all 15 ABC News Australia section slugs, names, and URLs accepted by abcau-headlines. Use this to discover valid sections like Just In, World, and Australia before fetching headlines.

Instructions

Get ABC News Australia sections. Lists the 15 ABC News Australia section slugs accepted by abcau-headlines, from justin and world to backstory and australia. Each entry has a slug, a display name (for example Just In) 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.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 behavioral burden. It discloses useful output details: there are 15 entries, each with a slug, display name, and page URL. It does not explicitly state that the operation is read-only or mention error behavior, but for a zero-parameter lookup the disclosure is largely sufficient.

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 compact sentences. It front-loads the core purpose and follows with the return structure and sibling relationship. Every sentence adds value without 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 tool has no parameters, no output schema, and no annotations, the description supplies the key missing context: what the sections are, how many there are, and what fields each entry contains. An agent has enough information to call the tool and interpret its response.

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 has zero parameters, so the baseline is 4. The description appropriately does not discuss parameter semantics, and no additional parameter meaning 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?

The description states a specific verb and resource: it gets ABC News Australia sections. It also distinguishes this tool from sibling tools by explaining that it lists the 15 section slugs accepted by abcau-headlines. An agent can easily tell this is a section-lookup tool rather than a headlines/news/article tool.

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 usage context by tying the tool to abcau-headlines: it provides the slugs accepted by that sibling. It does not explicitly state when not to use this tool or mention alternatives beyond abcau-headlines, but the intended use is clear.

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