Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_get_wallet · Orbitx

orbitx__orbitx_get_wallet
Read-only

Wallet portfolio: SOL balance, holdings, realized/unrealized PnL. — Orbitx's MCP server, a live seat on The Wall (hosted by them). Called through their seat; their data comes back as it is. Read-shaped tools only (anything that buys, sells or writes refuses). Listing: https://rokha.ai/registry?skill=orbitx-official-mcp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNoSolana wallet. Omit to use the linked agent wallet.
authCodeNoOrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / properties
      Added value: +{
+  "address": {
+    "description": "Solana wallet. Omit to use the linked agent wallet.",
+    "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"
+  }
+}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds behavioral context: 'Called through their seat; their data comes back as it is' warns about pass-through data fidelity, and 'Read-shaped tools only (anything that buys, sells or writes refuses)' reinforces write refusal. These details add value over the annotations, though they are not extensive.

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

Conciseness3/5

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

The first sentence is front-loaded and clear, but the description includes a registry URL and server-context phrasing ('Orbitx's MCP server, a live seat on The Wall') that do not directly support tool invocation. It is not overly long, but not every sentence earns its place.

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?

With no output schema, the description lists the key return components (SOL balance, holdings, realized/unrealized PnL) and provides a data-fidelity caveat. This is adequate for a simple read-only portfolio tool, though it omits potential error conditions or availability details.

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%, and the description does not provide additional parameter-level meaning. The address and authCode parameters are already fully documented in the input schema, so the description adds no extra semantic value beyond the baseline.

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 states a specific resource and data content: 'Wallet portfolio: SOL balance, holdings, realized/unrealized PnL.' This is a clear verb+resource statement, though it does not explicitly differentiate from sibling tools like orbitx__orbitx_get_balance, which may partially overlap.

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 provided on when to use this tool versus sibling get_* tools. The only related statement, 'Read-shaped tools only (anything that buys, sells or writes refuses),' is a server-wide constraint that does not help with tool selection, leaving usage to be inferred solely from the title and first sentence.

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
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