Crawlora MCP

thehill_article

Read-only

Fetch one public The Hill article's metadata and body paragraphs. Use thehill_headlines to discover story cards. Use thehill_news for the general news feed.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical The Hill article URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / url / description
```
Added value: +"Canonical The Hill article URL"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the read-only and open-world profile. The description adds value beyond that by disclosing the article is 'public' (no authentication needed) and that the response contains 'metadata and body paragraphs.' It does not mention rate limits or pagination, but those gaps are minor given the annotations.

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?

Three short, front-loaded sentences with zero waste: the action first, then the two sibling alternatives. Every sentence earns its place.

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 one-parameter fetch tool with an output schema and annotations, the description covers purpose, auth context, and sibling routing adequately. Return details are delegated to the output schema, so nothing essential is missing.

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 single url parameter is already documented as a 'Canonical The Hill article URL.' The description references 'one public The Hill article' but adds no syntax or format guidance beyond the schema, so baseline 3 applies.

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: 'Fetch one public The Hill article's metadata and body paragraphs.' It distinguishes this single-article fetcher from the discovery/feed siblings by naming thehill_headlines and thehill_news, though it leaves 'metadata' loosely defined.

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?

Explicitly routes the agent: use thehill_headlines to discover story cards and thehill_news for the general feed, implying this tool is for retrieving a known article URL. Clear context, but no explicit statement of when NOT to use it or the required URL prerequisite.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?