Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

nationalpost_news

Fetch National Post top stories to monitor news: returns 10 current articles across all sections with titles, URLs, summaries, publication times, and bylines.

Instructions

Get National Post top stories. Returns the latest 10 National Post stories across all sections, with no parameters. Each item has a title, canonical article URL, one-line summary, publication time and byline. Use nationalpost-headlines to read a single section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose meaningful traits: fixed return size (latest 10), no parameters, all-sections scope, and the exact per-item fields (title, canonical URL, one-line summary, publication time, byline). It stops short of stating freshness guarantees, auth requirements, or pagination behavior, which for a read-only news list is a modest but real gap.

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 tight sentences, front-loaded with the purpose and scope, then the return shape, then the alternative-tool routing. Every sentence earns its place; there is no filler.

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 zero-parameter, no-output-schema news list tool this is complete: scope, fixed count, item fields, and the routing alternative to the section-scoped sibling are all stated. An agent has everything needed to call it correctly and interpret the response.

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. The description confirms this explicitly ("with no parameters"), so there is nothing for it to clarify beyond the schema, but it correctly closes off the expectation that filters or section arguments exist.

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+resource ("Get National Post top stories") and immediately bounds the scope: latest 10 stories, across all sections, no parameters. It differentiates itself from the sibling nationalpost_headlines by clarifying that this one spans all sections while that one reads a single section.

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?

Explicitly names an alternative and the condition that selects it: "Use `nationalpost-headlines` to read a single section." This is a clear when-not-this-tool signal. The only blemish is that the sibling is referred to with a hyphen rather than the actual `nationalpost_headlines` underscore form, which could mildly confuse an agent already aware of the sibling list.

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