Skip to main content
Glama

vanguardng_author

Read-only

Recent Vanguard articles credited to a byline in one public feed (Vanguard has no author profile pages): title, URL, byline, and publish time.

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

Input Schema

NameRequiredDescriptionDefault
nameYesByline to look for (3 to 80 characters), e.g. Chioma Obinna
sectionNoOptional section slug to scan instead of the site-wide feed. 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. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Byline to look for (3 to 80 characters), e.g. Chioma Obinna"
    • addedInput schema / properties / section / description
      Added value: +"Optional section slug to scan instead of the site-wide feed. 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
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. Beyond that, the description adds real behavioral context: results are limited to a single public feed and to 'recent' items, and notably that Vanguard has no author profile pages, which tells the agent not to hunt for a richer profile source. No rate limit or pagination detail, but solid for the annotation coverage provided.

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 sentence that front-loads the core function and then parenthetically supplies the key limitation and the returned fields. No filler, nothing redundant.

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 not be detailed, and annotations cover the safety profile; the description nonetheless adds the useful 'no author profile pages' caveat. What remains thin is routing guidance relative to the article/news/headlines siblings and the effect of the section parameter, keeping it just short of 5.

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 description coverage is 100% – both 'name' (byline, 3-80 chars, with example) and 'section' (with a full documented slug list) are already fully explained in the schema. The description's phrase 'one public feed' faintly gestures at the site-wide vs section feed choice but adds no syntax or default behavior beyond the schema. Baseline 3 is correct.

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 and resource: 'Recent Vanguard articles credited to a byline,' which an agent can distinguish from vanguardng_article (single article), vanguardng_news/headlines (feed listings), and vanguardng_sections (section browsing). It also names the returned fields, reinforcing the scope. It stops short of explicitly naming a sibling to route away from, so 4 rather than 5.

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 only implied – an agent can infer this is the tool for 'given a byline, get their recent pieces' – but there is no explicit when-to-use statement, no mention of the alternative vanguardng_article when you already have a URL, and no guidance on when to prefer the section-scoped feed over the site-wide feed. Implied usage only.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.