Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_get_token · Orbitx

orbitx__orbitx_get_token
Read-only

Full token intel: price, market cap, holders, OG score, trust verdict, forensics summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYes
chainNosolana
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. 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"
+  },
+  "chain": {
+    "default": "solana",
+    "type": "string"
+  },
+  "mint": {
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "mint"
+]
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description makes no contradictory claims. It adds only the output category list and no extra behavioral disclosures such as data freshness or external calls, but this is acceptable for a read-only data lookup.

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?

One short sentence carries a meaningful payload of output fields and no filler. The key phrase 'Full token intel' is front-loaded and immediately communicates the tool's scope.

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 3 parameters, no output schema, and many overlapping siblings, the description is too thin: it does not state what input identifies the token, whether it is appropriate for a broad overview versus a specialized check, or anything about the authCode requirement beyond the schema. It lists output categories but leaves usage context unresolved.

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

Parameters1/5

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

Schema description coverage is only 33% (authCode is described, mint and chain are bare strings), and the description does not mention any parameters. The agent must infer that 'token' maps to the mint parameter; chain's meaning and authCode's role are left entirely to the schema.

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 names the resource (token) and lists concrete data fields (price, market cap, holders, OG score, trust verdict, forensics summary), making the intent clear. 'Full token intel' hints at a comprehensive role, though it does not explicitly distinguish itself from specialized siblings like get_forensics or get_safety.

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 statement of when to use this tool versus the many sibling get_* tools. The only usage signal is the name and 'full token intel', which is too weak to route an agent away from get_forensics, get_safety, or get_chart.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources