Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nationalpost_sections

Get all 45 National Post section slugs accepted by headline queries, with display names and category URLs, so you can pick valid sections and skip external or paid ones.

Instructions

Get National Post sections. Lists the 45 National Post section slugs accepted by nationalpost-headlines, such as canada, opinion, hockey and gift-guide, each with its display name and category page url. Links that leave nationalpost.com (Financial Post, Driving.ca, puzzles, classifieds, e-paper) and the paid Sponsored categories are not included.

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 disclosure burden and does well: it gives the count (45), the return shape (display `name` and page `url`), and the meaningful exclusions (off-site links like Financial Post/Driving.ca/puzzles/classifieds/e-paper, plus paid Sponsored categories). No auth or mutation concerns apply to a static listing, but it doesn't say whether the set is stable or when it might change.

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, then the schema hints, then the exclusions. No filler; every clause conveys usable 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?

For a zero-param listing with no output schema and no annotations, the description covers the return fields and the inclusion boundaries well. Minor residual gaps are ordering/completeness guarantees, but nothing blocks correct invocation.

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, so the baseline is 4. The description adds no parameter meaning (there are none), and mentions of slugs belong to a different tool, so no penalty or credit beyond the baseline.

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 ('Get'/'Lists') and resource ('National Post sections') and explicitly ties them to the sibling tool that consumes them: 'section slugs accepted by `nationalpost-headlines`'. An agent can immediately distinguish this from nationalpost_headlines/article siblings.

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 link to `nationalpost-headlines` strongly implies the use case (discover valid section slugs before fetching headlines), and it names what is excluded. It stops short of an explicit 'use this before calling nationalpost_headlines' instruction, so the routing is inferred rather than stated.

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