Skip to main content
Glama
Sign In

proof-of-custody

by io.github.onrampbtc
OverviewDiscussionsAdmin

route_question

Routing table lookup. Given a bitcoin custody or market-structure question, returns the matching route: the situation it belongs to, the custody models in play, the Proof of Custody page that answers it, which tool on this server to call next, and the primary sources for the facts with their refresh cadence. Use first when a question is broad or you are unsure which tool applies.

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": {
      "question": "<question>"
    },
    "name": "route_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax routes (default 3).
questionYesThe question as the person asked it.

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?

With no annotations, the description carries the disclosure burden and largely meets it: it describes the shape of the response (situation, models, page, recommended next tool, sources with refresh cadence) and the default route cap via the schema. It does not explicitly state that this is a read-only lookup with no side effects, leaving that to inference from 'lookup'.

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

Conciseness5/5

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

Front-loaded with a two-word identity, then what it returns, then when to use it. The enumeration is long but earns its place because there is no output schema, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter router with no output schema and no annotations, the description supplies everything an agent needs: trigger condition, return payload contents, and the fact that the returned route names the next tool to call. Nothing material is missing.

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% and both parameters are documented there, including the default of 3 for limit. The description adds no additional semantics for 'question' (e.g., whether natural-language phrasing or keywords work better) or for how limit interacts with route ranking, so it sits at the baseline.

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 ('routing table lookup', 'returns the matching route') and enumerates exactly what the route contains: situation, custody models, Proof of Custody page, next tool, and sources. This clearly distinguishes it from the many retrieval/evaluation siblings, which perform the actual lookups rather than routing.

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?

Gives an explicit trigger: 'Use first when a question is broad or you are unsure which tool applies.' That is a concrete selection condition against the sibling tools. It stops short of stating the inverse (when you already know the target tool, skip this), so not a full 5.

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

All proof-of-custody 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