Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vox_headlines

Fetch current Vox headlines by section, returning each item's title, URL, summary, author, and publication time.

Instructions

Get Vox section headlines. Lists the current Vox headlines for one section. section is required and takes politics, culture, policy, world, money, technology, science-and-health, climate, future-perfect or explainers. Each item has its title, URL, summary, author and publication time.

Input Schema

NameRequiredDescriptionDefault
sectionYesVox section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose the shape of returned items (title, URL, summary, author, publication time) plus the 'current' freshness constraint. It omits any note on rate limits or whether results are paginated, but for a simple read-only list feed this is solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action before the parameter and return details. Slightly redundant in re-listing all ten enum values that the schema already provides, but no wasted prose.

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?

For a single-parameter, enum-constrained feed tool with no output schema, the description covers the action, the required input, valid values, and the fields returned per item. An agent needs nothing more to call it correctly.

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 coverage is 100% and the enum already enumerates all valid section slugs, so the description's restatement of the same ten values adds no new syntax or semantics. Baseline 3 applies when the schema does the work.

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: 'Get Vox section headlines' / 'Lists the current Vox headlines for one section.' An agent can tell this is a section-scoped headline lister. It does not explicitly name or distinguish itself from siblings like vox_sections or vox_news, so it falls just short of a 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 implied by 'for one section' and the required section param, but there is no explicit when-to-use guidance, no prerequisites, and no named alternatives (e.g., 'use vox_sections to discover valid sections'). Minimum viable.

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