Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehill_news

Fetch current top stories from The Hill as structured JSON, including titles, URLs, summaries, authors, and publication times. Use it to monitor U.S. political news headlines without scraping.

Instructions

Get The Hill top stories. Returns the current top stories from The Hill. It takes no parameters. Each item has its title, URL and, where the outlet gives them, a summary, author, publication time, image URL and type. Use the headlines endpoint to read one section instead.

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?

No annotations are provided, so the description must carry the behavioral burden. It correctly states that the tool takes no parameters and describes the shape and optionality of returned items ('where the outlet gives them'), which is meaningful context absent an output schema. It does not discuss rate limits or authentication, but for a simple read-only news feed this is largely self-evident.

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

Conciseness3/5

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

The description is front-loaded and easy to scan, but the first two sentences are redundant: 'Get The Hill top stories' and 'Returns the current top stories from The Hill' say the same thing. Trimming that repetition would make every sentence earn its place.

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 zero-parameter, no-output-schema tool, the description covers everything an agent needs: what it returns, that it has no inputs, the fields present on each item, and the alternative for section-specific news. No essential behavior is left unspecified.

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 takes zero parameters, so the schema provides no parameter semantics to clarify. The description correctly confirms 'It takes no parameters,' matching the empty schema and preventing an agent from searching for undocumented inputs.

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?

States a specific verb ('Get') and resource ('The Hill top stories') and immediately distinguishes this from the headlines endpoint, which reads a single section. An agent can tell exactly what this tool returns versus its closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative tool ('the headlines endpoint') and the condition that selects it ('to read one section instead'). The implication is that this tool is for cross-section top stories, so the when-to-use/when-not-to-use boundary 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