Skip to main content
Glama

north_balance

Check the local NORTH wallet balance breakdown, including spendable funds, pending payments, immature block rewards, and open payment outcomes.

Instructions

What the wallet holds: NORTH that can be spent now, what is set aside for payments that are under way, block rewards that are not ripe yet, and the payments whose outcome is open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discharges part of it by enumerating the four categories returned, which is the most important behavioral fact since there is no output schema. It omits that this is a read-only, side-effect-free call, whether values are live or cached, and what happens if no wallet is configured.

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?

A single front-loaded sentence with no filler; every clause names one of the returned buckets. Slightly figurative phrasing ('not ripe yet', 'whose outcome is open') is the only cost, and it is compact enough to be worth it.

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 zero-parameter read tool with no output schema and no annotations, describing the shape of the result is the main thing needed, and that is done. It would be complete with one clause on read-only nature and whether the numbers are current or eventually consistent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is empty and consistent with the description's implicit 'query the configured wallet' semantics.

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 names the resource precisely: it returns the wallet's holdings broken into four named buckets (spendable NORTH, funds reserved for in-flight payments, unripe block rewards, and unresolved payments). The phrase 'What the wallet holds' implies a read, but no verb is ever stated and no sibling is contrasted, so it stops short of a top score.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative among the eleven siblings. An agent must infer that this is the balance-snapshot call and that north_limits or north_payments cover different questions.

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