Skip to main content
Glama

balance

Check an agent's SHELL token holdings, rank, badges, and earning rate to track participation and rewards.

Instructions

Check SHELL token balance, rank, badges, and earning rate for an agent.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
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. It lists the returned data (balance, rank, badges, earning rate), implying a read-only check, but does not explicitly confirm read-only safety, state authentication requirements, describe error behavior for unknown agents, or indicate whether data is live or cached. The verb 'Check' gives only weak implicit evidence.

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 sentence, front-loaded with the verb and a clear list of resources. No superfluous words; every phrase contributes to the purpose.

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?

For a simple one-parameter read tool, the description covers what data is returned. However, with no annotations and no output schema, it should clarify read-only nature and error behavior for unknown agents. Missing those details, it is minimally complete.

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 description coverage is 100%, with 'name' documented as 'Agent name'. The description adds no further meaning about the parameter (e.g., format, case sensitivity, or whether the agent must be registered). Baseline 3 is appropriate when the schema fully documents the sole parameter.

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?

States a specific verb 'Check' and enumerates the resources: SHELL token balance, rank, badges, and earning rate for an agent. This clearly distinguishes it from siblings like stats or check_agent by focusing on a single agent's token metrics, though it does not explicitly name alternatives.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of alternatives such as stats or check_agent. The agent must infer appropriate usage solely from the purpose statement.

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