Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_get_balance · Orbitx

orbitx__orbitx_get_balance
Read-only

Token or SOL balance for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintNoOptional token mint; omit for SOL
addressNo
authCodeNoOrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok). Auth contract: signing tools (backend-signed trades, launches, burns, NFT mints) accept EITHER a valid authCode OR an authenticated session (OAuth/API-key bearer from a linked chat). The 5-minute auto-fill sweep and other server-side jobs run under their own internal credential — they never take an authCode. An authCode is sufficient but not the only accepted credential; a missing/invalid credential is rejected, never silently trusted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / authCode / description
      Previous value: -"OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok)."New value: +"OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok). Auth contract: signing tools (backend-signed trades, launches, burns, NFT mints) accept EITHER a valid authCode OR an authenticated session (OAuth/API-key bearer from a linked chat). The 5-minute auto-fill sweep and other server-side jobs run under their own internal credential — they never take an authCode. An authCode is sufficient but not the only accepted credential; a missing/invalid credential is rejected, never silently trusted."
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / properties
      Added value: +{
+  "address": {
+    "type": "string"
+  },
+  "authCode": {
+    "description": "OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok).",
+    "type": "string"
+  },
+  "mint": {
+    "description": "Optional token mint; omit for SOL",
+    "type": "string"
+  }
+}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond the basic purpose—no mention of network behavior, error cases, or response format. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence with no filler, and the key distinction between token and SOL is front-loaded. It is concise, though slightly elliptical as a noun phrase rather than a full imperative sentence.

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

Completeness2/5

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

For a tool with no output schema and an undocumented address parameter, the description is too thin. It does not explicitly state that address is the wallet being queried, whether it is required, or what the response contains. The authCode requirement appears only in the schema, not in the description.

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 coverage is 67%; mint and authCode are documented in the schema. The description adds the relationship that omitting mint means SOL, but it does not clarify the address parameter, which has no schema description. This is adequate but does not fully compensate for the undocumented address.

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 clearly identifies the resource (balance) and scope (token or SOL for a wallet), which distinguishes it from sibling tools like orbitx_get_wallet or orbitx_get_token. It lacks an explicit verb, but the tool name supplies 'get', making the purpose unambiguous.

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?

No guidance is given on when to use this tool versus alternatives such as orbitx_get_wallet or singularityagent__balance. There are no conditions, exclusions, or context cues to help an agent choose this tool over similar ones.

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