Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thehill_headlines

Read-only

Current The Hill headlines for one public section; section must come from thehill_sections.

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": {
      "section": "<section>"
    },
    "name": "thehill_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Hill RSS section slug. Documented values: home, homenews, policy, business, opinion, healthcare, campaign, national-security, senate, house, administration, regulation, media, defense, technology, transportation, international, economy, policy-healthcare.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"The Hill RSS section slug. Documented values: home, homenews, policy, business, opinion, healthcare, campaign, national-security, senate, house, administration, regulation, media, defense, technology, transportation, international, economy, policy-healthcare."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are 'current' and limited to a single public section, but says nothing further about freshness, pagination, or limits.

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?

A single clause-pair sentence with the resource and the scoping constraint front-loaded; nothing is wasted.

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?

With an output schema present and annotations covering safety, the description only needs to convey scope and the input dependency, both of which it does. The mild gap is that it does not differentiate itself from thehill_news.

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% and the schema already lists documented section slugs, so baseline is 3. The description adds genuinely new meaning: the value must be sourced from thehill_sections, a constraint absent from the schema itself.

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 ('Current The Hill headlines') and scopes it to 'one public section'. It is clearly a filtered-headlines tool, though it never explicitly distinguishes itself from the sibling thehill_news.

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?

Provides a concrete prerequisite: the section must come from thehill_sections, which tells the agent how to obtain a valid input. It stops short of naming an alternative tool for other headline needs, so no exclusions.

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

All Crawlora MCP toolsInspect
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