Skip to main content
Glama

Best paid API for a need (free)

best_endpoint
Read-only

Free. Find the highest-scoring paid agent API (L402/x402) for a need, e.g. 'bitcoin price', 'weather forecast', 'stock quotes'. Returns up to limit ranked endpoints with URL, protocol, price and 0-100 quality score from BitTuitive's own probes.

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": {
      "need": "<need>"
    },
    "name": "best_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the API should provide (keywords).
limitNo
protocolNoOptional payment protocol filter.
data_typeNoOptional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is lighter; it still adds real context by disclosing the return shape (URL, protocol, price, 0-100 score) and that scores come from BitTuitive's own probes. It does not cover what happens with no matches or whether results are cached, which keeps it short of a 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?

Three tight sentences, front-loaded with the free/no-cost signal and then the purpose, then the return shape. No filler, though the leading 'Free.' fragment is slightly awkward as an opener.

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 output schema, the description correctly takes on the return-value burden and names the returned fields and score range. For a read-only lookup with 75% schema coverage, the remaining gap is empty-result and ranking-tie behavior, which is minor.

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 75% with enums for protocol and data_type already documented, so the schema carries most of the burden. The description adds only the meaning of limit ('up to `limit` ranked endpoints') and the ranking basis; it does not clarify keyword-matching behavior for `need`, which is the one required parameter.

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?

States a specific verb and resource: find the highest-scoring paid agent API (L402/x402) for a need, with concrete need examples ('bitcoin price', 'weather forecast'). This is clearly distinguishable from catalog/sibling tools like scoreboard_search or route_endpoints because it is a need-based ranked lookup.

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 implied by the need-based framing and the example queries, and 'Free.' signals there is no cost to calling it. However, it never states when to prefer this over scoreboard_search, route_endpoints, or the dedicated get_btc_price/get_weather_* tools, so the agent must infer routing.

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