Skip to main content
Glama

byte-protocol

by io.github.0rkz
OverviewDiscussionsAdmin

byte_get_token_balances

Read-onlyIdempotent

Get USDC and ETH balances for an address on Arbitrum Sepolia (the on-chain testnet layer — MockUSDC settles subscriptions and fact-oracle queries there). Does NOT show the Base-mainnet USDC balance that byte_buy_data spends.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEthereum address (0x...)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ethNoETH balance as a decimal string in whole ETH (e.g. '0.01') — already scaled by 18 decimals, not wei
usdcNoUSDC balance as a decimal string in whole USDC (e.g. '12.5') — already scaled by 6 decimals, not atomic units
addressNoEchoed address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / eth / description
      Previous value: -"ETH balance (wei)"New value: +"ETH balance as a decimal string in whole ETH (e.g. '0.01') — already scaled by 18 decimals, not wei"
    • changedOutput schema / properties / usdc / description
      Previous value: -"USDC balance (atomic, 6 decimals)"New value: +"USDC balance as a decimal string in whole USDC (e.g. '12.5') — already scaled by 6 decimals, not atomic units"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "description": "Echoed address",
+      "type": "string"
+    },
+    "eth": {
+      "description": "ETH balance (wei)",
+      "type": "string"
+    },
+    "usdc": {
+      "description": "USDC balance (atomic, 6 decimals)",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful network context about MockUSDC and settlement, but no additional behavioral traits like failure modes or response characteristics.

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?

Two sentences with no filler; the core scope is front-loaded and the clarifying exclusion follows immediately. Every sentence earns its place.

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 one fully documented parameter, a rich output schema, and annotations covering safety, the description is complete enough for correct invocation. It also covers the important cross-network distinction that could otherwise cause misuse.

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% for the single 'address' parameter, so the schema already fully documents it. The description does not add parameter-specific semantics beyond what the schema provides.

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?

States a specific verb and resource ('Get USDC and ETH balances for an address') with precise network scope (Arbitrum Sepolia) and explicit exclusion of Base-mainnet balances. Clearly differentiates from byte_buy_data.

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?

Explicitly says this tool does NOT return the Base-mainnet USDC balance that byte_buy_data spends, telling an agent when this tool is not appropriate. This gives clear routing guidance relative to a relevant sibling.

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

All byte-protocol toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources