Skip to main content
Glama
Sign In
MIDL MCP Server

MIDL MCP Server

Official
by midl-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

midl_get_token_balance

Read-only

Retrieve the ERC20 token balance of a wallet address along with token metadata (symbol, name, decimals).

Instructions

Get ERC20 token balance for an address. Returns balance along with token metadata (symbol, name, decimals).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tokenAddress": "<tokenAddress>",
      "ownerAddress": "<ownerAddress>"
    },
    "name": "midl_get_token_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYesERC20 token contract address
ownerAddressYesAddress to check balance for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral details beyond what annotations provide, which is acceptable but not extra value.

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 a single sentence of 13 words, front-loaded with the action and resource. Every word adds value, with no unnecessary fluff.

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 two-parameter tool with annotations and no output schema, the description adequately covers what the tool does and what it returns. It could optionally mention that the ownerAddress is an Ethereum address, but that is implied by the pattern in the schema.

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%, so the parameter descriptions in the schema already explain the two parameters. The tool description does not add additional meaning or constraints beyond what the schema provides, so baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'ERC20 token balance for an address', and specifies that it returns balance and token metadata. It effectively distinguishes from sibling tools like midl_get_evm_balance or 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?

The description implies that this tool is for ERC20 token balances, which is clear context. However, it does not explicitly exclude other token types or reference alternative tools for non-ERC20 balances, which would be helpful given the presence of similar sibling tools.

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