Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanguardng_news

Fetch Vanguard (Nigeria) top stories as structured JSON, returning 20 recent articles with titles, URLs, summaries, publication times and images.

Instructions

Get Vanguard top stories. Returns the latest 20 Vanguard (Nigeria) stories with no parameters. Each has a title, URL, summary, publication time and image where available. author is the site's account name, often a desk account such as Nwafor; use vanguardng-article for the on-page byline.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 well: it discloses the fixed result count (20), the returned fields (title, URL, summary, publication time, image), and critically clarifies that `author` is the site's desk account rather than a real byline. Auth, rate limits, and pagination are unaddressed, but for a public no-param feed this is substantial disclosure.

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 and scope, then return shape, then the one non-obvious field caveat. Nothing is redundant and every sentence carries 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?

With no output schema, the description usefully enumerates the returned fields and explains the ambiguous `author` value. It lacks any mention of freshness guarantees or how the feed is ordered beyond "latest," a minor gap for a top-stories endpoint.

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?

There are zero parameters, so the baseline is 4. The description correctly emphasizes that the tool takes no arguments, which prevents an agent from inventing inputs.

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 top stories") and immediately quantifies scope ("latest 20"). A reasonable agent can tell it returns a fixed feed, though it does not explicitly distinguish itself from the sibling vanguardng_headlines.

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?

The description notes there are no parameters and points to vanguardng-article for the on-page byline, which is a useful routing hint. However it never explains when to prefer this feed over vanguardng_headlines or vanguardng_sections, leaving the sibling choice implicit.

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