Skip to main content
Glama
Sign In

AgentReeve BTC Intelligence

by io.github.shakeelamjid
OverviewDiscussionsAdmin

btc_free_preview

Free, reduced-fidelity BTC summary: rounded spot/futures index, basis, venue dispersion, and how many sources are fresh. No payment required. Full detail is behind the paid routes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does real work: it says the values are rounded (so callers know not to treat them as exact), that no payment/auth is needed, and that source freshness is reported. It omits rate limits, caching/staleness timing, and whether output is stable across calls, which keeps it at 4 rather than 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?

Two sentences, front-loaded with the resource and the field list, with the paid-route caveat last. 'No payment required' mildly restates 'Free' from the opening, a small redundancy that keeps it from a 5.

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, no params, and no annotations, so the description must explain what comes back — and it does, itemizing the returned metrics including source freshness. It is nearly complete for this simple read tool; only caveats like rate limits or refresh cadence are missing.

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 there is nothing for the description to disambiguate; baseline is 4. The description sensibly spends its words on output shape instead of inventing parameter meaning.

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 concrete resource (a BTC summary) and enumerates what it contains: rounded spot/futures index, basis, venue dispersion, and fresh-source count. It also pins the tier (free, reduced-fidelity) and contrasts with 'paid routes,' so an agent knows it is getting a summary rather than full detail. It does not distinguish itself from the sibling btc_free_sample, which keeps it short of a 5.

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

Usage Guidelines4/5

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

'No payment required' plus 'Full detail is behind the paid routes' gives a clear selection rule: use this when a cheap/rounded view suffices and escalate for precision. It stops short of a 5 because the paid alternative is referred to generically rather than named, and no explicit when-not conditions are stated.

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

All AgentReeve BTC Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources