Skip to main content
Glama
Sign In
MIDL MCP Server

MIDL MCP Server

Official
by midl-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

midl_get_evm_balance

Read-only

Retrieve the BTC balance on the EVM layer. Provide an EVM address to query, or omit to use the connected wallet. Returns balance in wei and formatted BTC.

Instructions

Get the EVM layer BTC balance. If no address provided, returns balance of connected wallet. Returns balance in wei and formatted BTC.

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_evm_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoEVM address (0x...). If omitted, uses connected wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds return format (wei and formatted BTC) beyond annotations. No contradiction. No hidden side effects noted.

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 concise sentences front-loading purpose and key details. No wasted words.

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 simple read-only balance tool. Could mention network, but not required.

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 describes parameter well. Description adds no new info beyond schema, but matches schema's default behavior.

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 the EVM layer BTC balance' with verb and resource. Distinguishes from sibling tools like midl_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 Guidelines4/5

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

Specifies behavior when address is omitted vs provided, giving clear usage context. Does not explicitly exclude other use cases but adequate.

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