Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sevennewsau_news

Retrieve 7NEWS Australia top stories from all sections; returns 100 recent items with title, URL, summary, publication time, image, and author. No input required.

Instructions

Get 7NEWS Australia top stories. Returns the 100 most recent 7NEWS Australia stories across every section, with no input needed. Each item has its title, canonical URL, summary, publication time, lead image, and the author when one is credited. Agency copy is often credited to Digital Staff.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 reasonably well: it discloses the exact result count (100), the no-input behavior, the fields returned, and the 'Digital Staff' author-credit quirk. It does not mention pagination, refresh cadence, or any rate/authentication constraints, but for a read-only news feed this is largely sufficient context.

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?

Three tightly written sentences, front-loaded with the core purpose, then scope, then return contents. No filler; every sentence adds information the agent can use.

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?

With no output schema and no annotations, the description must describe returns, and it does so field-by-field, which is complete enough to call the tool correctly. Minor gaps remain around pagination/ordering beyond the implied 'most recent' and how it relates to sibling fetch tools.

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, so the baseline is 4. The description correctly frames the absence of inputs, and there is nothing further to document.

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 7NEWS Australia top stories') and defines scope as the 100 most recent stories across every section. It does not explicitly differentiate itself from sibling tools like sevennewsau_headlines or sevennewsau_sections, leaving the agent to infer the boundary.

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?

'with no input needed' effectively tells the agent this is a zero-argument call, which is useful. However, there is no guidance on when to choose this over sevennewsau_headlines, sevennewsau_sections, or sevennewsau_article, so the routing decision is left to inference.

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