Skip to main content
Glama

TechCrunch AI News — buy per-query in-session (techcrunchai)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: techcrunchai: TechCrunch AI — industry news, funding & launches. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are today's biggest AI industry news stories?; Any AI funding rounds or model launches announced this week?. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description adds context annotations cannot express: no API key required, 0.01 USDC/query pricing, and a max of 20 queries/session. That auth/rate-limit/cost detail is genuinely useful behavioral context beyond the structured fields.

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 lead sentence and pricing are front-loaded, but the message is marketing-flavored and redundant, repeating the no-key/no-payment point twice ("No API key needed" then "FREE preview — no key, no payment") and padding with sample questions and a checkmark. It is not bloated to the point of harm, but several phrases are boilerplate rather than informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read-only tool with rich annotations and no output schema, the description covers cost, auth, and limits adequately. It still omits what the preview actually returns and how it relates to the paid query path, which is the main thing an agent needs before choosing between the two.

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%, with both the slug routing behavior and the optional echoed question fully documented in the schema itself. The description adds no syntax, format, or defaulting guidance for either parameter, so the schema does all the work and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the specific listing being sampled (techcrunchai: TechCrunch AI — industry news, funding & launches) and frames the tool as a "FREE preview," but it never states plainly that it returns only public listing metadata as opposed to actual query results. The verb is implied by the word "preview" rather than stated outright, so an agent must infer what the call produces.

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

Usage Guidelines2/5

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

There is a soft call to action ("Try one of the sample questions now") and pricing framing that hints the tool is a free precursor to a paid query, but no sibling is named and no explicit when-to-use/when-not rule is given. The agent is left to infer on its own that data_session_query is the paid alternative and that this tool should be used first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources