Skip to main content
Glama

BitTuitive prices and plans (free)

bittuitive_pricing
Read-only

Free. BitTuitive's paid endpoints, per-call prices in sats, subscription plans, and live status.

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": "bittuitive_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already establish that this is a safe, self-contained read, so the description does not need to restate safety. It does add two things annotations cannot: the call is free of charge, and the response includes live status (i.e., data freshness). It does not disclose response shape, caching, or size, but with no output schema and a simple zero-arg read, the bar is modest.

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?

One short, front-loaded line with no filler. The bare-fragment "Free." and the trailing noun list read telegraphically rather than as a complete sentence, a minor polish issue rather than a comprehension problem.

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 no parameters and no output schema, the description carries the burden of saying what comes back, and it does: prices, plans, and live status. Only the return format and whether status is per-endpoint are left undefined, which is a small gap for a free read-only lookup.

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?

The tool takes zero parameters, so the baseline is 4. Nothing in the description suggests hidden or implicit inputs, consistent with the empty input schema.

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?

"BitTuitive's paid endpoints, per-call prices in sats, subscription plans, and live status" names a concrete resource and enumerates its contents, so the agent knows this is a pricing/plan catalog. It lacks an explicit verb ("returns"/"lists") and does not name a sibling it is distinct from, but no sibling in the catalog plausibly overlaps with pricing.

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

Usage Guidelines3/5

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

"Free." and the reference to "paid endpoints" imply the intended call pattern (check cost before invoking billable endpoints), but the description never states when to use this versus route_call, request_data, or best_endpoint. Usage is inferable rather than instructed.

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