Skip to main content
Glama
Sign In
btcmatic-mcp-server

btcmatic-mcp-server

Official
by btcmatic-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Prepaid balance

btcmatic_credits

Check your prepaid token's balance and remaining call coverage to monitor usage and avoid unexpected interruptions.

Instructions

Free. The balance behind the configured prepaid token (BTCMATIC_AGENT_TOKEN) and how many calls it still covers.

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

Input Schema

NameRequiredDescriptionDefault
tokenNoOverride the configured token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It does disclose that the operation is free and what it returns, but it does not explicitly state that it is read-only or describe any side-effect-free behavior.

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?

The description is only two short sentence fragments, front-loaded with the most important fact (free) followed by a clear purpose statement. Every word earns its place with no redundancy.

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?

For a simple tool with one optional parameter and no output schema, the description covers the essential purpose, cost, and return value (remaining calls). It is complete enough for an agent to invoke it correctly, though it could mention relationship to topup tools.

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% for the single optional 'token' parameter, which already has a description ('Override the configured token'). The tool description adds no additional parameter semantics beyond what the schema provides, so 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 states the tool returns the balance behind the configured prepaid token and how many calls it covers. This clearly differentiates it from the sibling topup tools, though it lacks an explicit verb like 'check' or 'get'.

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

Usage Guidelines2/5

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

The description says 'Free' but gives no explicit guidance on when to use this tool versus the topup siblings. There is no mention of checking balance before topping up or any exclusions.

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

Deploy Server

Other Tools