Crawlora MCP

smh_news

Read-only

Returns The Sydney Morning Herald's current public "Latest News" feed (about 20 stories): title, canonical URL, summary, author, publication time (UTC), and lead image; returns headline items from the general top-story stream. For a section-specific list, use smh_headlines with a supported section slug. Use smh_sections to discover section slugs. Use smh_article with a returned article URL when you need one story's body.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smh_news"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that this is a live public feed of ~20 headline items with UTC timestamps and lead images, which helps set expectations for freshness and payload shape, though it says nothing about caching or retrieval latency.

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?

Front-loads purpose and payload in the first clause, then chains the alternative-routing guidance in order of relevance. Four tight clauses with no filler; 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?

An output schema exists, so the description need not explain returns, yet it briefly lists fields without over-specifying. For a zero-param feed tool with safety annotations covered, an agent has everything needed to call 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 tool takes zero parameters (empty object, additionalProperties false), so there is no per-parameter syntax to document. Baseline 4 applies; the description correctly signals no filtering is available and points to smh_headlines for narrower queries.

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 and resource ('Returns The Sydney Morning Herald's current public Latest News feed'), quantifies it (~20 stories), and enumerates the returned fields. It explicitly distinguishes itself from smh_headlines (section-specific) and smh_article (single story), so an agent can select it without opening a sibling schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use smh_headlines for a section-specific list, smh_sections to discover slugs, and smh_article with a returned URL for a single story body. When-to-use and alternatives are all stated, nothing left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?