Skip to main content
Glama
Sign In
MIDL MCP Server

MIDL MCP Server

Official
by midl-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

midl_get_utxos

Read-only

Retrieve unspent transaction outputs (UTXOs) for a Bitcoin address or the connected wallet's payment address.

Instructions

Get unspent transaction outputs (UTXOs). If no address provided, uses connected wallet payment address.

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

Input Schema

NameRequiredDescriptionDefault
addressNoBitcoin address. If omitted, uses connected wallet payment address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive. Description adds that omitted address defaults to connected wallet payment address, which is useful behavioral context not in annotations.

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?

Single sentence, no fluff, front-loaded with purpose. Every word earns its place.

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?

Lacks output format or return value description, which could be helpful. However, tool is simple and name implies UTXO list. Adequate but not complete.

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 description coverage is 100%, so baseline is 3. The description repeats the address parameter's behavior already in the schema, adding no new semantic information.

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?

Clearly states 'Get unspent transaction outputs (UTXOs)' with specific verb and resource. The description also notes default behavior for address parameter, distinguishing it from related tools like get_btc_balance.

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?

Provides some guidance: default address from connected wallet. However, lacks explicit when-to-use vs alternatives, such as when to use this over get_btc_balance or get_transaction.

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