Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

globalnews_news

Fetch top stories from Global News (globalnews.ca) to check current headlines, with titles, URLs, summaries, authors, publication times, and images when provided.

Instructions

Get Global News top stories. Returns the latest top stories from Global News (globalnews.ca), with no parameters. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them, so it works as a quick check on what the outlet is leading with.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so reasonably: it states there are no parameters and enumerates the returned fields (title, URL, summary, author, publication time, image) with the caveat 'when the outlet provides them'. It omits any note on caching, rate limits, or how many stories are returned, but for a zero-param read-only feed 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?

Two front-loaded sentences: the first says what it is, the second says what you get. No filler. The second sentence is a little long and leans on the vague closing phrase, but it stays efficient.

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?

There is no output schema, so the description must describe the return payload, and it does so field by field. Combined with the explicit statement that there are no inputs, an agent has enough to call and interpret the tool correctly; only item count/pagination is unaddressed.

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, which is the baseline-4 case, and the description explicitly confirms this ('with no parameters'). Nothing further is required or useful here.

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 Global News top stories') and pins the source domain (globalnews.ca), so the agent knows exactly what feed it returns. It does not, however, differentiate itself from close siblings like globalnews_headlines or globalnews_article, leaving the agent to guess which one is the 'top stories' feed.

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?

The closing clause ('works as a quick check on what the outlet is leading with') gives a plausible use case, which is more than nothing. But it names no alternatives and gives no exclusion criteria, so an agent choosing between this and globalnews_headlines, globalnews_sections, or globalnews_article has to infer.

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