Skip to main content
Glama
joelklabo

Maximum Sats MCP

by joelklabo
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

ask_bitcoin

Get answers to Bitcoin and Lightning Network questions using AI-powered insights with Lightning Network micro-payments.

Instructions

Ask a question about Bitcoin, Lightning Network, or cryptocurrency. Powered by Llama 3.3 70B. Costs 21 sats via Lightning L402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesYour question about Bitcoin or Lightning
payment_hashNoPayment hash if retrying after L402 payment

Implementation Reference

  • src/index.ts:93-104 (handler)
    Registration and handler implementation for the "ask_bitcoin" tool.
    server.tool(
  "ask_bitcoin",
  "Ask a question about Bitcoin, Lightning Network, or cryptocurrency. Powered by Llama 3.3 70B. Costs 21 sats via Lightning L402.",
  {
    prompt: z.string().describe("Your question about Bitcoin or Lightning"),
    payment_hash: z.string().optional().describe("Payment hash if retrying after L402 payment"),
  },
  async ({ prompt, payment_hash }) => {
    const data = await l402Post(MAXIMUMSATS_API, "/api/dvm", { prompt }, payment_hash);
    return textResult(data.result || formatL402(data));
  }
);

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

No annotations provided, but description carries the burden well by disclosing: AI model (Llama 3.3 70B), cost (21 sats), and payment mechanism (Lightning L402). Critical behavioral info for a paid tool. Does not disclose output format or error handling.

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?

Two front-loaded sentences with zero waste: purpose first, implementation details second. Every word earns its place. No redundancy with schema or name.

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?

Adequate for a 2-parameter Q&A tool with 100% schema coverage. Critical omission would be payment details, which are included. Only minor gap is lack of output format description (though 'ask' implies text response).

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?

Schema coverage is 100%, but description adds crucial context for 'payment_hash' by explaining the L402 payment flow and cost ('21 sats via Lightning L402'), giving semantic meaning to why the parameter exists beyond the schema's technical definition.

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?

Clear verb ('Ask') + specific resources ('Bitcoin, Lightning Network, or cryptocurrency'). Distinct from Web of Trust siblings (wot_*) and generate_image through explicit domain scoping in first sentence.

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?

Defines the domain (Bitcoin/crypto questions) providing implicit usage guidance, but lacks explicit when-to-use vs alternatives (e.g., doesn't clarify when to use this vs querying WOT data directly). No exclusion criteria or prerequisites mentioned beyond payment.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joelklabo/maximumsats-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server