Skip to main content
Glama

t2000_balance

Retrieve an AI agent's current financial balance including checking, savings, credit, gas reserve, and net total in USD.

Instructions

Get agent's current balance — available (checking), savings, credit (debt), gas reserve, and net total. All values in USD. For a full account snapshot, prefer t2000_overview instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 't2000_balance' tool, which retrieves the agent's current balance information using the agent.balance() method.
    server.tool(
      't2000_balance',
      "Get agent's current balance — available (checking), savings, credit (debt), gas reserve, and net total. All values in USD. For a full account snapshot, prefer t2000_overview instead.",
      {},
      async () => {
        try {
          const result = await agent.balance();
          return { content: [{ type: 'text', text: JSON.stringify(result) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates this is a read operation ('Get') and specifies the currency (USD), but it does not mention other behavioral traits such as authentication requirements, rate limits, error conditions, or whether the data is real-time or cached. The description adds some context but leaves gaps in behavioral transparency.

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 concise and well-structured, consisting of two sentences that efficiently convey the tool's purpose, output details, and usage guidelines without any wasted words. It is front-loaded with the core functionality and follows with contextual advice.

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?

Given the tool's complexity (simple read operation with no parameters) and lack of annotations and output schema, the description is mostly complete. It covers what the tool does, its output components, currency, and when to use it versus an alternative. However, it does not describe the return format or any potential errors, which could be helpful for an agent invoking the tool.

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 has 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description does not discuss parameters, which is appropriate, but it could have noted the lack of parameters explicitly. A baseline score of 4 is applied as the description compensates adequately by focusing on output semantics instead.

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's purpose with a specific verb ('Get') and resource ('agent's current balance'), listing the exact components retrieved (checking, savings, credit, gas reserve, net total) and currency (USD). It effectively distinguishes this tool from its sibling 't2000_overview' by specifying this is for balance details only, not a full account snapshot.

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

Usage Guidelines5/5

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

The description explicitly provides usage guidance by stating 'For a full account snapshot, prefer t2000_overview instead,' which clearly indicates when to use this tool (for balance details) versus an alternative (for broader account information). This direct comparison helps the agent make correct tool selections.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server