Skip to main content
Glama

get_max_spendable

Read-only

Maximum BTC (sats) an address can send to an onramp after estimated network fees.

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": {
      "address": "<address>"
    },
    "name": "get_max_spendable"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBitcoin address

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?

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context — the result is net of estimated (not final) network fees and is expressed in sats — but says nothing about fee estimation freshness, whether onramp limits or dust thresholds are factored in, or how the estimate is derived.

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?

One sentence, front-loaded with the returned quantity and immediately qualified by the unit and the fee deduction. Nothing is redundant or padded.

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 one simple parameter, no output schema, and annotations covering read-only behavior, the description carries the key missing piece — what the returned number means and in what unit. It stops short of noting that the figure depends on a live fee estimate and is therefore volatile, which an agent deciding when to re-call would want.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents the address input. The description clarifies that the address is the sending side whose balance is being measured, which is marginal added meaning over 'Bitcoin address'.

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 computed resource: the maximum BTC, denominated in sats, that a given address can send to an onramp after estimated network fees. That is far more specific than the name alone and separates it from quote/route siblings, though it never explicitly names an alternative.

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: an agent can infer this is the pre-flight check for 'how much can I actually send'. There is no explicit when-to-use, no statement of when to prefer get_quote or get_routes instead, and no prerequisites such as needing a funded address.

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