Skip to main content
Glama

Request a data type BitTuitive does not have yet (free)

request_data

Free. Tell BitTuitive what data you want (data_type, description, an example query, and the max price in sats you would pay). This records a demand signal only; it does not add a source or bypass the paywall. New sources need a clearly legal, redistributable origin and an operator go-ahead. Ranked counts are the paid get_market_insights tool; public /api/v1/insights/* pages are teasers only.

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": {
      "data_type": "<data_type>",
      "description": "<description>"
    },
    "name": "request_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactNoOptional email so an operator can follow up. Never published.
data_typeYesCategory, e.g. weather, stocks, traffic, other.
descriptionYesWhat you need and why it would help.
example_queryNoAn example query or URL shape you would send.
max_price_satsNoMax sats you would pay per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and idempotentHint=false, so the description carries real weight and does: it declares the tool free, declares that a submission is a record-only write with no immediate data effect, and states the prerequisites for anything to be built (legal redistributable origin plus operator go-ahead). It does not say what a repeat submission does given idempotentHint=false, or what response the caller gets back.

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

Conciseness4/5

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

Front-loaded with 'Free.' followed by what to submit, then the scope limit and the alternative. Dense but each sentence carries distinct information; the closing sentence on paid insights versus public teasers is the only part that verges on adjacency trivia.

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 five-parameter mutation with no output schema and thin annotations, the description covers intent, scope limits, cost, and gating conditions well. The remaining gap is what the caller receives after submitting and whether duplicate requests are deduplicated.

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%, so the schema already documents all five parameters including the 'never published' note on contact and the per-call meaning of max_price_sats. The description restates the parameter list (data_type, description, example query, max price in sats) without adding format guidance beyond what the schema provides, so the baseline 3 applies.

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?

Specific verb plus resource: submit a demand request for a data type BitTuitive doesn't have, with the payload enumerated. It sharply distinguishes itself from the siblings that actually return data by stating 'This records a demand signal only; it does not add a source or bypass the paywall.' An agent can tell immediately that this is not a fetch tool.

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?

Gives the when ('tell BitTuitive what data you want'), the when-not ('does not add a source or bypass the paywall'), and routes to an alternative for a related need ('ranked counts are the paid get_market_insights tool'). It also pre-empts a false expectation by noting the public insights pages are teasers only.

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