Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

vanguardng_article

Read-only

Returns public Vanguard article metadata and body paragraphs from a canonical article URL. Vanguard has no paywall. url: Canonical Vanguard article URL. Use vanguardng_headlines to get Vanguard section headlines.

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": {
      "url": "<url>"
    },
    "name": "vanguardng_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Vanguard article URL

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 / url / description
      Added value: +"Canonical Vanguard article URL"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already declared, the bar is lower, and the description adds salient context: 'Vanguard has no paywall,' implying no auth and full body text availability. It doesn't disclose rate limits, partial-fetch behavior, or error handling on non-canonical URLs, but it meaningfully supplements the annotations.

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?

Three short sentences, front-loaded with the purpose, followed by the paywall note and the sibling pointer. The 'url: Canonical Vanguard article URL' clause duplicates the schema text and is mild waste, but overall it is tight.

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 needn't be explained, and annotations cover the safety profile. For a single-required-param, read-only fetch tool the description covers purpose, alternative routing, and paywall status, leaving only minor gaps around URL validation and failure modes.

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?

Only one parameter with 100% schema description coverage, so the schema already documents 'Canonical Vanguard article URL.' The description repeats that phrasing verbatim without adding format, validation, or canonicalization guidance, so the 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?

States a specific verb (Returns) and a concrete resource (public Vanguard article metadata and body paragraphs) sourced from a canonical URL. It partially differentiates from siblings by noting the headlines tool, but doesn't distinguish itself from vanguardng_news, vanguardng_sections or vanguardng_author, so an agent must infer that boundary.

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?

Explicitly routes the agent to vanguardng_headlines for section headlines, giving a clear condition for choosing the alternative. It stops short of stating when *not* to use this tool (e.g., browsing vs fetching a specific article), so it's clear context without full exclusions.

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