Skip to main content
Glama
Sign In
tonnode/mcp

tonnode/mcp

by tonnode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_balance

Retrieve the native GRAM balance of any TON address in GRAM and nano units. Pass either a friendly or raw address.

Instructions

Native GRAM balance of an address (GRAM is the renamed Toncoin), in both GRAM and nano units.

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": {
      "address": "<address>"
    },
    "name": "get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesTON address in friendly (EQ…/UQ…) or raw (0:…) form

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided. The description adds value by noting the return includes both GRAM and nano units, but lacks disclosure of behavior like network calls, error handling, or idempotency. Basic but not insufficient.

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?

Extremely concise single sentence that is front-loaded with the tool's purpose. No extraneous words.

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 simple tool with one parameter and no output schema, the description is adequate but lacks detail on the response format. For a read operation, stating it returns a numeric balance in both units is helpful, but explicit mention of the data structure would improve completeness.

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% with a clear parameter description. The description does not add additional meaning to the address parameter beyond what the schema already provides. Baseline score of 3 applies.

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 tool retrieves the native GRAM balance of an address, specifying the resource and units. It distinguishes from siblings like get_account_state (which may include balance but is more general) or get_transactions (different operation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. For example, get_account_state might also provide balance information, so explicit context on prioritizing this over others would help.

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