Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Get balances for a set of addresses across many chains

singularityagent__portfolio
Read-only

Query one address, or a whole set of them, across many chains in parallel. Pass addresses when somebody holds an EVM address, a Solana pubkey and a Bitcoin address — that is one person's holdings and would otherwise be three separate questions. Each address is matched only to the chains its own format is valid on, so this is not a cross product and a Solana pubkey never produces twenty EVM errors; an address valid nowhere is reported in errors rather than failing the call. holdings is the consolidated view, by asset rather than by chain. It sums only where a sum is honest: the same token, on the same chain, across the addresses you gave. It never adds a token to itself across chains — USDC on Ethereum and USDC on Base are different contracts with different issuers of record — and never merges two contracts because they share a ticker, since only symbols this tool supplies itself are grouped by name at all. spansChains marks an asset found in more than one place. Read completeness before concluding anything is absent. Balances only: there is no fiat pricing and therefore no total value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoHow much of each list to return: 'small' (10 items, for a tight context), 'standard' (the default), 'full' (this source's maximum), or a number for an exact count. Omitting it changes nothing. Anything cut is reported in `completeness` as truncated with counts, never dropped silently.
chainsNoChains to query. Defaults to a spread of major chains across all four families.
addressNoOne address, ENS/SNS name, or configured alias. Use `addresses` for a set.
addressesNoSeveral addresses, which may span chain families. Deduplicated before querying.
includeTokensNoSet false for native balances only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "address": {
+    "description": "One address, ENS/SNS name, or configured alias. Use `addresses` for a set.",
+    "type": "string"
+  },
+  "addresses": {
+    "description": "Several addresses, which may span chain families. Deduplicated before querying.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "budget": {
+    "description": "How much of each list to return: 'small' (10 items, for a tight context), 'standard' (the default), 'full' (this source's maximum), or a number for an exact count. Omitting it changes nothing. Anything cut is reported in `completeness` as truncated with counts, never dropped silently.",
+    "type": [
+      "string",
+      "number"
+    ]
+  },
+  "chains": {
+    "description": "Chains to query. Defaults to a spread of major chains across all four families.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "includeTokens": {
+    "description": "Set false for native balances only.",
+    "type": "boolean"
+  }
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description reveals important behaviors: parallel querying, per-address chain matching that avoids cross-product errors, invalid addresses being reported in `errors`, consolidated `holdings` semantics, no cross-chain token summing, `spansChains` marking, and the need to read `completeness`. This is rich, honest behavioral disclosure.

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 dense but every sentence earns its place. It is front-loaded with the core purpose, then moves through usage, matching behavior, consolidation rules, completeness caveat, and exclusions. No fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates well by explaining key output concepts: `errors`, `holdings`, `spansChains`, and `completeness`. It also clarifies the no-fiat-pricing limitation and the honest-summing behavior. An agent has enough context to invoke the tool correctly and interpret results.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the intended use of `addresses` versus `address`, how address-chain matching works, and how invalid addresses are handled. It does not deeply explain `budget` or `includeTokens`, but those are already well described in the schema.

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 states a specific verb and resource: query balances for one address or a set of addresses across many chains. It clearly distinguishes this from single-chain balance tools and explains the multi-chain, parallel nature of the operation.

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 gives explicit guidance on when to use the `addresses` parameter (when one person holds addresses across EVM, Solana, and Bitcoin) and states an exclusion (no fiat pricing, so no total value). It does not name sibling tools like `singularityagent__balance` as alternatives, but the guidance is otherwise clear.

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

All Rokha toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources