Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

globeandmail_headlines

Fetch Globe and Mail headlines for a specified section, returning each story's title, URL, summary, author, publication time, and lead image.

Instructions

Get the latest stories in a Globe and Mail section. Returns the current public feed for one Globe and Mail section: each story's title, canonical URL, summary, author, publication time, and lead image. Section must be one of the slugs returned by /globeandmail/sections: canada, world, business, investing, personal-finance, politics, opinion, culture, sports, life, real-estate, drive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesGlobe and Mail section slug from /globeandmail/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does state this is a 'current public feed' and lists what it returns, which implies a safe read operation. However, it does not disclose pagination, rate limits, freshness bounds, or explicitly confirm no side effects or authentication requirements.

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?

Two dense sentences front-load the action and resource, then cover return fields and valid inputs. There is no filler, and the valid slug list is placed at the end where it is useful without obstructing the main purpose.

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 single-parameter read tool with no output schema, the description is complete: it states the operation, scope, acceptable values, and the exact fields returned. An agent can select and invoke this tool correctly without additional lookup, especially since the valid slugs are fully enumerated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as a Globe and Mail section slug. The description adds the context that each slug selects a section feed, but it does not materially go beyond the schema's enum and description, so baseline 3 is appropriate.

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?

The description clearly identifies the tool as fetching the latest stories for a Globe and Mail section and enumerates the returned story fields. It is unambiguous about the resource and action, though it does not explicitly contrast itself with siblings like globeandmail_news or globeandmail_sections.

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

Usage Guidelines4/5

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

The description gives clear context: this returns a section feed, accepts exactly one section slug, and lists all valid values. It does not explicitly state when to prefer a sibling tool, but the precondition and valid input range are clearly communicated.

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