Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanguardng_article

Fetch a Vanguard Nigeria article by its canonical vanguardngr.com /YYYY/MM/slug/ URL and return title, section, authors, image, and body paragraphs as JSON; feeds and section pages are rejected.

Instructions

Get Vanguard article content. Returns one Vanguard (Nigeria) story by its url, a vanguardngr.com link in the /YYYY/MM/<slug>/ form; section pages and feeds are rejected. The response has the title, description, times, section, authors, lead image and body paragraphs. Vanguard has no paywall, so paywalled is never set.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Vanguard article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 reasonably well: it discloses the response shape (title, description, times, section, authors, lead image, body paragraphs), the URL validation behavior, and the non-obvious fact that Vanguard has no paywall so `paywalled` is never set. It omits auth, rate-limit, or error behavior, keeping it short of a 5.

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 purpose, then constraint, then response shape. No redundancy; each sentence adds information the agent needs.

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?

With no output schema provided, the description usefully enumerates the returned fields, and it covers input validation, publisher scope, and paywall status. Nothing essential for correctly calling a single-URL article-fetch tool 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 100%, so the baseline is 3, but the description adds meaning beyond the schema's terse 'Canonical Vanguard article URL' by specifying the exact URL pattern (`/YYYY/MM/<slug>/`) and the accepted domain, which helps an agent construct or validate the argument.

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 Vanguard article content', 'Returns one Vanguard (Nigeria) story by its url') and identifies the publisher and content type precisely. It is easily distinguished from sibling tools like vanguardng_headlines, vanguardng_news, and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Constrains usage concretely: the url must be a vanguardngr.com link in `/YYYY/MM/<slug>/` form, and 'section pages and feeds are rejected', which implicitly routes the agent away from section/feed tools. It stops short of naming a specific alternative tool by name, so it gives clear context but no explicit sibling routing.

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