Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brisbanetimes_sections

List Brisbane Times editorial sections with exact path slugs, menu labels, and requested URLs to find article-bearing pages and populated topic hubs.

Instructions

Get Brisbane Times editorial sections. Lists the 104 accepted Brisbane Times editorial surfaces (95 article-bearing section pages and nine populated topic hubs), each with its exact path slug, menu label, and requested Brisbane Times URL. Three linkless surfaces with no explicit empty-state marker are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/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 well: it discloses the exact result count, the composition of the list, the fields per entry, and the exclusion rule ('three linkless surfaces with no explicit empty-state marker are excluded'). It does not mention pagination, caching, or return format, but for a static read-only listing that is a minor gap.

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 sentences, front-loaded with the action and scope, then the counts and fields, then the exclusion rule. Every sentence earns its place, though the precise counts (104/95/9) are arguably denser than needed for tool selection.

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?

No output schema or parameters exist, so the description must convey the return shape, and it does: it describes the count and per-entry fields (slug, label, URL). Missing an explicit statement of output format/ordering, but an agent has enough to call and use it 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 schema has zero parameters, so the baseline is 4. The description adds context about what the parameterless call yields (104 entries with three named fields), which is more than the empty schema provides.

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 ('Get') and resource ('Brisbane Times editorial sections'), then quantifies the output (104 surfaces: 95 section pages plus 9 topic hubs) and names the fields returned (path slug, menu label, URL). This clearly separates it from siblings like brisbanetimes_article, brisbanetimes_headlines, and brisbanetimes_news.

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?

Usage is implied: this is the enumeration tool for Brisbane Times coverage areas, and the description explains what it returns. However, it never states when to prefer it over brisbanetimes_headlines or brisbanetimes_news, nor any prerequisites or follow-up steps, so an agent must infer the workflow.

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