Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brisbanetimes_headlines

Fetch current headlines from a Brisbane Times section or topic by providing a valid section slug; unsupported paths are rejected.

Instructions

Get Brisbane Times section or topic headlines. Returns current story cards from one observed Brisbane Times server-rendered section or populated topic page. section must be one of the exact slugs from /brisbanetimes/sections; unsupported and unresolved linkless paths are rejected before an upstream request. Off-brand story links on Traveller are omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection or topic slug from /brisbanetimes/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 add real behavioral context: input is validated and rejected before any upstream request, one section/topic page is fetched, and off-brand Traveller links are filtered out. It omits pagination, rate limits, and result ordering, but goes beyond merely restating the schema.

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?

Three front-loaded sentences with the action stated first and constraints after; nothing is padded. Slight redundancy between 'section or topic headlines' and 'section or populated topic page' keeps it from a 5.

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 headline lister with no output schema and no annotations, the description covers what it returns (story cards), the scope (one section/topic page), and the main failure mode (unsupported/linkless paths). It is complete enough to call correctly, with only minor gaps around result volume and ordering.

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 description coverage is effectively 100% (the single enum parameter is documented as 'Section or topic slug from /brisbanetimes/sections'), so the baseline is 3. The description reinforces the exact-slug constraint and the pre-request rejection behavior, which adds modest value but no new format or syntax detail.

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 Brisbane Times section or topic headlines') and clarifies the return unit ('current story cards from one observed ... section or populated topic page'). An agent can tell it is a listing tool, though it never names the sibling it differs from (e.g., brisbanetimes_news vs brisbanetimes_article), so differentiation is inferential.

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?

Provides an important prerequisite ('section must be one of the exact slugs from /brisbanetimes/sections') and notes that unsupported paths are rejected. However, it never states when to prefer this over brisbanetimes_news, brisbanetimes_sections, or brisbanetimes_article, so usage is implied rather than directed.

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