Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_get_ath · Orbitx

orbitx__orbitx_get_ath
Read-only

All-time-high price and market cap for a token. — 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

B3.1/5.0
Behavior4/5

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

Annotations already mark the tool read-only and non-destructive. The description adds a concrete behavioral detail: mutating calls coming through this seat are refused, and data is returned as-is without normalization. This is useful context beyond the annotations, though it omits output format and error behavior.

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 tight and front-loaded with the tool's purpose. The middle sentences about the hosting seat and read-only policy are partly boilerplate, and the listing URL is navigation context rather than invocation guidance. It is not bloated, but not every sentence earns functional weight.

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?

The tool is simple and has no output schema, and the description does convey the core result: ATH price and market cap. However, it doesn't mention that a mint is required, what fields the output contains, or how the authCode is used beyond what the schema already says.

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 50%, with authCode documented but the required mint parameter undocumented. The description only says 'for a token' and does not explain the mint field's format or requirement, so it does not compensate for the missing schema coverage.

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 states the tool's outcome: all-time-high price and market cap for a token. It distinguishes the tool from sibling Orbitx get_* tools like get_chart or get_balance, though it does not explicitly name an alternative.

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?

There is no guidance about when to choose this tool over sibling get_token, get_chart, or get_signals. The 'Read-shaped tools only' statement is a general server constraint, not a usage rule or an explicit alternative condition.

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