Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanguardng_headlines

Retrieve up to 20 recent Vanguard headlines for a specified section. Each item includes title, URL, summary, author, and publication time.

Instructions

Get Vanguard section headlines. Lists up to 20 recent Vanguard stories from one category. section is required and takes one of 42 slugs such as national-news, politics, business, sports, business/energy or more/metro. Items carry title, URL, summary, author and publication time. An unknown section returns an invalid-params error.

Input Schema

NameRequiredDescriptionDefault
sectionYesVanguard section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 does useful work: it caps results at 20, states that section is required, and discloses that an unknown section returns an invalid-params error. It also names the fields each item carries. It omits auth needs and any rate-limit/pagination behavior.

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?

Four short sentences, purpose and scope front-loaded, then parameter detail, then error behavior and item shape. The opening two sentences overlap slightly ('Get Vanguard section headlines' / 'Lists up to 20 recent Vanguard stories from one category'), but nothing is wasted.

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 required enum parameter with no output schema, the description covers everything an agent needs: scope, the result cap, valid value patterns, error behavior, and the item fields returned. Nothing material is missing.

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?

Schema coverage is already 100% and the enum lists all 42 slugs, so baseline is 3. The description adds value by giving representative slug examples (including the nested 'business/energy' and 'more/metro' patterns) and by documenting the invalid-params failure mode for unknown values.

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+resource ('Get Vanguard section headlines') and defines scope precisely as 'up to 20 recent Vanguard stories from one category.' An agent can distinguish this from an article-fetch tool, though it never explicitly contrasts itself with sibling vanguardng_news or vanguardng_sections.

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?

Usage is implied by the scope ('stories from one category'), which tells an agent this is a per-section listing rather than a search. There is no explicit when-to-use guidance, no mention of when to prefer vanguardng_news or vanguardng_article, and no stated prerequisites.

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