Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_crypto_scan · Orbitx

orbitx__orbitx_crypto_scan
Read-only

One-shot aggregator: safety + forensics + token payload for a mint. — 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
mintYes
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. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / properties
      Added value: +{
+  "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": {
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "mint"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Read-shaped tools only (anything that buys, sells or writes refuses)' and 'their data comes back as it is', offering concrete behavioral context beyond the annotations. It clarifies the external hosting and raw data nature, which is valuable.

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 opening sentence is purposeful and front-loaded. However, the description includes extraneous context like 'Orbitx's MCP server, a live seat on The Wall (hosted by them).' and a URL to a registry listing, which aren't needed for tool invocation. It could be trimmed to the purpose and read-only enforcement without losing value.

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?

Given it's an aggregator with no output schema, the description should clarify what to expect in response. It names the three payload types but not their structure or how they're combined. It also omits any mention of the authCode requirement, which is critical for usage. The basic purpose is clear but operational details are incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% (authCode described, mint not). The description says nothing about the parameters themselves; it does not explain what 'mint' refers to or how to obtain/use authCode. The authCode is described in the schema, but the description adds no additional meaning for either parameter.

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 clearly states the tool is a 'one-shot aggregator' for 'safety + forensics + token payload for a mint', providing a specific verb (aggregate) and resource. It distinguishes from sibling tools like orbitx_get_safety or orbitx_get_forensics by combining them into one call, so an agent can select it correctly without seeing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'one-shot aggregator' implies use when you need all three data types at once, but there is no explicit guidance on when to use this versus calling the specialized sibling tools separately, nor any exclusions or alternatives named. The read-only note is generic, not specific to this tool.

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