Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

smh_headlines

Fetch current Sydney Morning Herald headlines for a chosen section, returning story details like title, URL, summary, author, and publication time.

Instructions

Get The Sydney Morning Herald section headlines. Returns the current stories for one Sydney Morning Herald section: title, canonical URL, summary, author, publication time, and image where the section lists them. section must be one of the slugs returned by /smh/sections; any other value is rejected with a 400 before The Sydney Morning Herald is contacted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug from /smh/sections

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 behavioral burden, and it does so well by disclosing the return fields and the validation behavior: invalid sections are rejected with a 400 before the source is contacted. It does not mention rate limits or auth, but these are not clearly required for a simple read endpoint.

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, no filler, with the most important scoping and validation information front-loaded. Every sentence earns its place.

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 simple one-parameter tool with no output schema, the description is complete: it states the input source, the validation rule, and all expected return fields. An agent has enough to invoke it correctly and understand the response shape.

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?

Schema coverage is 100% and the enum plus parameter description already define valid values. The description adds value beyond the schema by explaining that the slug must come from /smh/sections and that invalid values cause a 400, giving the agent actionable validation context.

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?

The description states a specific verb ('Get') and resource ('The Sydney Morning Herald section headlines'), and enumerates exactly what is returned. It also differentiates from siblings by scoping to a single section and referencing /smh/sections, so an agent can tell it apart from smh_article, smh_author, and smh_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?

The description clearly says the tool returns current stories for one SMH section and explicitly instructs that the section must come from /smh/sections. It does not explicitly name alternative tools like smh_article for full articles, but the usage context is clear enough for correct selection.

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