Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sbsnews_sections

List valid SBS News sections for headlines requests, including primary navigation, Top Stories, and topic pages, each with slug, name, and URL.

Instructions

Get SBS News sections. Lists the SBS News sections that sbsnews-headlines accepts: the seven primary navigation sections, the Top Stories feed and featured topic and collection pages. Each entry has a slug, a display name and a url. News Podcasts and video surfaces are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/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 well: it discloses the return shape (`slug`, display `name`, `url`) and the exact scope boundaries (seven primary nav sections, Top Stories feed, topic and collection pages; no podcasts or video). It does not explicitly state that the call is a side-effect-free read, but for a zero-parameter listing tool that is a minor omission.

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 core purpose, followed by scope and output shape. Every sentence earns its place: purpose, coverage boundaries, entry structure, and exclusions.

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, but the description compensates by naming the fields each entry contains (`slug`, `name`, `url`) and by delineating what is and is not covered. For a zero-parameter discovery tool with no annotations, this is complete enough to call correctly.

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 is 4. The description appropriately spends no effort on parameter semantics and instead documents the returned fields, which is the relevant information for a zero-arg tool.

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 SBS News sections') and immediately scopes it as the enumeration of sections that `sbsnews-headlines` accepts. It distinguishes itself from siblings by naming the dependent tool and by carving out what is not included (podcasts, video surfaces).

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 makes the use case clear: this is the lookup for valid section inputs to `sbsnews-headlines`. It also states exclusions (News Podcasts and video surfaces), which prevents wrong selections. It stops short of naming an explicit alternative tool to use instead for those excluded surfaces, so it is not a full 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