btcpayserver-mcp

get_service_info

Discover available BTCPayServer services and their methods to explore what payment processing, store management, and administrative operations are available.

Instructions

Discover available BTCPayServer services and their methods. Use this to explore what operations are available.

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

Input Schema

Name	Required	Description	Default
`serviceName`	No	Optional: Get info for a specific service (e.g., "payment-requests", "invoices", "lightning"). If not provided, lists all services.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2025

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool 'discovers' and 'explores', which suggests a read-only operation, but doesn't explicitly state whether it's safe, whether it requires authentication, what format the output returns, or any rate limits. This leaves significant behavioral gaps for an agent.

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 perfectly concise with two clear sentences that directly state the purpose and usage without any wasted words. It's front-loaded with the core functionality and efficiently communicates essential information.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description is reasonably complete for a discovery tool. However, it lacks details about output format and doesn't fully compensate for the absence of annotations, leaving some contextual gaps for an agent trying to use this tool effectively.

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?

The input schema has 100% description coverage, so the schema already fully documents the single optional parameter. The description doesn't add any additional meaning about parameters beyond what's in the schema, but since schema coverage is high, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose with the verb 'discover' and resource 'available BTCPayServer services and their methods', making it easy to understand what the tool does. However, it doesn't explicitly distinguish this from its sibling tools (btcpay_request, get_method_info), which would be needed for a perfect score.

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?

The description provides some usage guidance with 'Use this to explore what operations are available', which implies this is for discovery purposes. However, it doesn't explicitly state when to use this tool versus its siblings (btcpay_request, get_method_info) or provide any exclusion criteria, leaving room for ambiguity.

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

Deploy Server