Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanguardng_sections

Lists all 42 Vanguard sections with slugs, display names, and feed URLs so you can choose valid categories for Vanguard headlines requests. Takes no parameters.

Instructions

Get Vanguard sections. Lists the 42 Vanguard sections accepted by vanguardng-headlines. Each has a slug (nested categories contain a /, as in business/energy), a display name and a feed url. national-news is the site's News category and promoted is sponsored content. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, the description carries the full burden and does well for a simple list endpoint: it states the count, return fields (slug, name, url), and special semantic cases like nested slugs and sponsored content. It does not mention auth or caching behavior, but for a zero-parameter read-only listing the disclosure is otherwise solid.

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 front-loaded with purpose and count, then adds only useful details about return fields and special cases, ending with a no-params note. Every sentence earns its place and there is no repetition or filler.

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?

Given the simple complexity, lack of annotations, and lack of output schema, the description provides everything an agent needs: what it lists, how many, the return shape, nested slug syntax, and special categories. It fully compensates for the absence of structured metadata.

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?

The tool has zero parameters, and the description explicitly states 'Takes no parameters,' which matches the empty input schema. With no parameters to document, the baseline score of 4 is appropriate.

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 description uses a specific verb and resource: 'Get Vanguard sections' and immediately clarifies it 'Lists the 42 Vanguard sections accepted by vanguardng-headlines.' It distinguishes itself from the sibling headlines tool by specifying that these are the section slugs accepted by that endpoint. An agent can tell what this tool returns without opening the schema.

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 clearly links this tool to vanguardng-headlines by saying these are the sections it accepts, which implies it should be used to discover valid section values. It does not explicitly state when not to use it or name alternative tools for browsing sections, but the context for usage is clear.

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