Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbc_news

Fetch top stories from CBC with title, URL, publication time, byline, and lead image; skips video, radio, music, books, and live-update pages.

Instructions

Get CBC News top stories. Returns fresh CBC News top stories with no input needed: title, canonical story URL, publication time, byline when given and lead image. Only stories the article endpoint accepts are returned, so video player pages, CBC Radio, Music and Books links and live-updates pages are omitted.

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 full burden, and it does meaningful work: it discloses the exact output shape (title, canonical URL, publication time, byline, lead image) and, notably, the content-exclusion rules (video player pages, radio, music, books, live-updates). It omits auth, rate-limit and pagination behavior, but the filtering disclosure is genuinely informative behavior beyond the schema.

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, purpose stated first and the exclusion rules last, so it is front-loaded and reasonably tight. The opening two sentences overlap slightly ('Get CBC News top stories' followed by 'Returns fresh CBC News top stories'), a minor redundancy.

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 compensates by describing the return fields and the filtering behavior, which is what an agent needs for this zero-arg tool. Lacking only cross-sibling routing and freshness/caching expectations.

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?

Zero parameters, so the baseline is 4. The description confirms no input is required, which matches the empty schema and removes any doubt about whether arguments are needed.

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 CBC News top stories') and enumerates the returned fields, which is more than a restatement of the name. It distinguishes itself from the article-fetching endpoint by noting only article-acceptable stories are returned, though it does not explicitly contrast with the close sibling cbc_headlines.

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?

'No input needed' implies this is the zero-argument browse-the-front-page call, which is usable guidance. However, it never states when to prefer this over cbc_headlines, cbc_sections or cbc_article, so selection among the CBC siblings 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