Skip to main content
Glama

APIs BitTuitive can call for you (free)

route_endpoints
Read-only

Free. Every scoreboard-verified L402 API the BitTuitive router can call on your behalf right now, grouped by data type, with upstream price, BitTuitive fee and the all-in price in sats.

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

Input Schema

NameRequiredDescriptionDefault
data_typeNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description nonetheless adds substantive context an agent could not infer: the listing is free, entries are scoreboard-verified, availability is live ('right now'), and each entry carries upstream price, BitTuitive fee and an all-in sats price. It does not say whether the list is paginated or cached, which keeps it below 5.

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 dense sentence with zero filler, and the cost signal ('Free.') is front-loaded. It is a noun phrase rather than a verb-led statement, which slightly slows the read but costs no correctness.

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?

There is no output schema, so the description must carry the return shape, and it does: grouping by data type plus the three price fields returned per entry. What remains unstated (ordering, result count, pagination) is minor for a small read-only catalog call.

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?

With a single parameter at 100% schema coverage and an explicit enum, the schema already does the work. 'Grouped by data type' loosely echoes the data_type filter but adds no syntax or behavioral detail beyond it, 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 names a specific resource with precise qualifiers: 'every scoreboard-verified L402 API the BitTuitive router can call on your behalf right now.' An agent knows this is a catalog/listing tool rather than an execution tool, though no sibling (route_call, best_endpoint, scoreboard_search) is named to sharpen the contrast.

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?

Usage is only implied: 'the router can call on your behalf right now' suggests this is a discovery step before invoking route_call or best_endpoint, but the description never says when to pick this over those siblings or what condition selects an alternative.

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