Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vanguardng_headlines

Read-only

Current Vanguard headlines for one public section; section must come from vanguardng_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "vanguardng_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesVanguard section slug. Documented values: national-news, top-stories, more-news, politics, business, business/energy, business/insurance-and-you, sports, entertainment, health, education-2, technology, innovation-2, aviation, agric, motoring, pension, foreign, editorial, opinion, columns, viewpoints, discourse, features, special-reports, thearts, cartoons, romance-an-relationships, homes-property, travel-and-tourism, style/allure/interviews, tribute, promoted, videos, top-podcasts, national-news/icymi, more, more/education, more/interview, more/labour, more/law-and-human-rights, more/metro.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"Vanguard section slug. Documented values: national-news, top-stories, more-news, politics, business, business/energy, business/insurance-and-you, sports, entertainment, health, education-2, technology, innovation-2, aviation, agric, motoring, pension, foreign, editorial, opinion, columns, viewpoints, discourse, features, special-reports, thearts, cartoons, romance-an-relationships, homes-property, travel-and-tourism, style/allure/interviews, tribute, promoted, videos, top-podcasts, national-news/icymi, more, more/education, more/interview, more/labour, more/law-and-human-rights, more/metro."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and freshness profile is largely covered. 'Current' adds a freshness signal and 'one public section' clarifies single-section scope, but nothing is said about result count, ordering, or pagination.

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?

A single compact sentence with the resource front-loaded and the constraint attached; there is no filler and every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the one required parameter is fully documented in the schema. The description suffices for a simple section-scoped headline feed.

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 section property documents all valid slugs extensively. The description only reinforces the source constraint ('must come from vanguardng_sections'), so the baseline 3 applies when the schema already carries the parameter meaning.

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: 'Current Vanguard headlines for one public section.' An agent can distinguish this from vanguardng_news or vanguardng_article by the headlines/section combination, though it never explicitly contrasts them.

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?

Provides a clear prerequisite and routing rule: 'section must come from vanguardng_sections,' which tells the agent to call a sibling first. There is no explicit when-not guidance, but the context is unambiguous for a single-param retrieval tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources