Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sbsnews_headlines

Fetch current SBS News headlines for a specified section. Provide a section slug from 15 options to get titles, URLs, and summaries for sections like top or world.

Instructions

Get SBS News section headlines. Returns current SBS News headlines for one section. section is required and takes one of 15 slugs from sbsnews-sections, such as top, latest, australia, world, politics, indigenous, cost-of-living or sport. Every item has its title and URL. The top, latest, australia and world sections also include summary, publication time and image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug from sbsnews-sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningfully disclose the return shape: every item has title and URL, and top/latest/australia/world additionally include summary, publication time and image. That is useful behavioral context, though it omits volume/pagination or freshness guarantees.

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?

Front-loaded with the verb and resource, then details. Four tight sentences with little waste, though the example slug list is somewhat redundant against the enum.

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 single-parameter, no-output-schema tool, the description supplies both the call constraint (one required section) and the return contents, which is nearly everything an agent needs to call it correctly. It only lacks explicit sibling routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a full enum, so the schema already documents the parameter; the description only adds the origin of the slugs (sbsnews-sections) and a subset of examples. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 section headlines') and narrows scope to a single section. It implicitly separates itself from sbsnews_article/sbsnews_news by describing headlines, but does not explicitly name or route away from those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that `section` is required and must be one of 15 slugs (referencing sbsnews-sections), which implies the call pattern, but gives no explicit when-to-use vs alternatives or prerequisites (e.g., 'call sbsnews_sections first to enumerate slugs, use sbsnews_article for full text').

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