Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbc_sections

List all 35 CBC News sections and their slugs, names, and feed URLs accepted by cbc-headlines for national, regional, or sports feeds.

Instructions

Get CBC News sections. Lists the 35 CBC News sections that cbc-headlines accepts: 8 national desks such as politics and world, 21 regional newsrooms such as toronto and nova-scotia, and 6 CBC Sports feeds such as sports-nhl. Each has a slug, a display name and the feed url. Top stories come from cbc-news, not a section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return shape (each entry has `slug`, display `name`, and feed `url`) and the fixed size/composition of the result set. It's a read-only enumeration with no auth or mutation concerns, so little more is needed.

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 compact sentences, front-loaded with the core action, then the composition breakdown, then the sibling exclusion. Every clause carries information.

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?

Complete for a parameterless listing tool: the agent knows the cardinality, the categories, the returned fields, and where top stories live instead. Without an output schema the field disclosure in the description is what makes it sufficient.

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 of 4 applies. The description adds context about what each returned record contains, which is the relevant 'parameter' information here.

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 and resource ('Get CBC News sections') and immediately quantifies the scope (35 sections split 8 national / 21 regional / 6 sports). It also distinguishes itself from siblings by naming `cbc-headlines` as the consumer and `cbc-news` as the top-stories source.

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?

Implies the workflow ('the 35 sections that `cbc-headlines` accepts') and explicitly redirects top stories to `cbc-news` rather than a section. Clear context, though it doesn't spell out a hard 'call this before cbc-headlines' rule or any when-not conditions beyond the top-stories exclusion.

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