Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanguardng_author

Find recent Vanguard articles credited to a specific byline. Since Vanguard lacks author profile pages, it scans public feeds, site-wide or by section.

Instructions

Find recent Vanguard articles by byline. Vanguard publishes no author profile pages, so this returns the recent articles in one public feed (site-wide by default, or one section) credited to a byline, matched on the on-page "By " line or the site's creator field.

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does disclose the essential behavior: no profile pages, site-wide or section feed, and matching on the on-page Byline or the site's creator field. It does not describe the output shape or pagination, but for a straightforward read-only feed lookup this is adequate.

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?

The description is two sentences with the purpose front-loaded. The second sentence packs scoping and matching detail efficiently without redundancy or filler.

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?

For a two-parameter lookup tool, the description covers what it finds, where it searches, and how matching works, with the section enum provided by the schema. The main gap is the lack of an output schema or any description of return fields, which keeps it from being fully complete.

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. It explains that the optional section overrides the default site-wide scan, and it specifies what the name is matched against: the on-page By line or creator field.

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?

The opening sentence names a specific verb, resource, and criterion: 'Find recent Vanguard articles by byline.' This is unambiguous and clearly distinguishes the author-lookup tool from the site's article tool and from other author tools by naming Vanguard explicitly.

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?

The description explains that Vanguard has no author profile pages, which tells the agent why this tool exists and what it returns: one public feed. It also clarifies the scope option ('site-wide by default, or one section'). It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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