Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

techcrunch_headlines

Read-only

Current TechCrunch headlines for one public section; section must come from techcrunch_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": "techcrunch_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesTechCrunch category slug. Documented values: apps, artificial-intelligence, biotech-health, climate, commerce, cryptocurrency, enterprise, fintech, fundraising, gadgets, gaming, government-policy, hardware, media-entertainment, privacy, robotics, security, social, space, startups, transportation, venture.

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: +"TechCrunch category slug. Documented values: apps, artificial-intelligence, biotech-health, climate, commerce, cryptocurrency, enterprise, fintech, fundraising, gadgets, gaming, government-policy, hardware, media-entertainment, privacy, robotics, security, social, space, startups, transportation, venture."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds only that results are 'current' and that the section is 'public', which is marginal context and says nothing about result volume or freshness windows.

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 tight sentence with the resource and the scoping constraint front-loaded; nothing is wasted and no filler precedes the operative information.

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?

An output schema exists, so return-value descriptions are unnecessary, and the one required parameter dependency is called out. For a single-param read tool the definition is nearly complete, missing only a note on ordering/recency or volume.

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 description coverage is 100%: the section slug and all documented values are fully enumerated in the schema. The description reinforces the provenance of the value ('must come from techcrunch_sections') but adds no syntax or format detail beyond the schema, so the 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?

The description states a specific verb and resource ('Current TechCrunch headlines') scoped to 'one public section', which distinguishes it from techcrunch_sections (which enumerates sections) and techcrunch_article (single item). It does not explicitly contrast with the sibling techcrunch_news, leaving some ambiguity about the headline-list vs. broader news feed.

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?

It gives a clear prerequisite: the section must be drawn from techcrunch_sections, routing the agent to the enumerating tool first. It stops short of stating when to prefer this over techcrunch_news or techcrunch_article, so it lacks explicit alternatives.

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