Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newscomau_sections

Retrieve News.com.au section slugs, display names, and listing URLs to locate categories. Pass a returned slug as the section parameter to fetch headlines.

Instructions

Get News.com.au sections. Returns the full News.com.au section/category navigation inventory (236 entries as of 2026-09-23), each with a slug, display name, and public listing URL. Use a returned slug as the section parameter on GET /newscomau/headlines.

Input Schema

TableJSON 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?

With no annotations, the description carries the transparency burden, and it does so well by disclosing that this is a 'Get' returning the full 236-entry inventory, each entry containing a slug, display name, and public listing URL, plus an as-of date. It does not discuss auth or rate limits, but those are not material for a zero-parameter catalog fetch.

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 sentences cover what the tool returns, the size and date of the dataset, the item fields, and the intended downstream use. It is front-loaded and contains 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?

For a zero-parameter catalog tool with no output schema, the description is sufficient: it names the exact fields in each result and states how to consume the returned slug. Nothing essential is missing for correct invocation.

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 input schema is empty and there are no parameters to document, so the baseline is 4. The description's mention of using a returned slug downstream adds useful context even though that slug is not an input to this 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 concrete verb and resource ('Get News.com.au sections') and then specifies the deliverable: the full section/category navigation inventory. This clearly differentiates it from sibling headline/article/news tools like newscomau_headlines and newscomau_news.

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?

Tells the agent exactly why the returned data matters: a slug should be used as the section parameter on GET /newscomau/headlines. This gives clear downstream context, though it does not explicitly contrast this tool with alternative section tools or state when not to use it.

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