Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_dex_chart · Orbitx

orbitx__orbitx_dex_chart
Read-only

HIGH QUALITY DexScreener embed chart for chat. When the user shares a CA/mint and asks for a chart, graph, DexScreener, or candles — call this immediately. Reso — 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
caNoToken contract address (mint CA) or DexScreener pair address
mintNoAlias of ca
chainNoChain id (default solana). Examples: solana, ethereum, base, bscsolana
themeNodark
iframeNoInclude HTML iframe block in markdown for clients that render HTML
authCodeNoOrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok).
intervalNoChart timeframe for the embed15m

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • 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"
+  },
+  "ca": {
+    "description": "Token contract address (mint CA) or DexScreener pair address",
+    "type": "string"
+  },
+  "chain": {
+    "default": "solana",
+    "description": "Chain id (default solana). Examples: solana, ethereum, base, bsc",
+    "type": "string"
+  },
+  "iframe": {
+    "default": true,
+    "description": "Include HTML iframe block in markdown for clients that render HTML",
+    "type": "boolean"
+  },
+  "interval": {
+    "default": "15m",
+    "description": "Chart timeframe for the embed",
+    "enum": [
+      "1m",
+      "5m",
+      "15m",
+      "1h",
+      "4h",
+      "12h",
+      "24h"
+    ],
+    "type": "string"
+  },
+  "mint": {
+    "description": "Alias of ca",
+    "type": "string"
+  },
+  "theme": {
+    "default": "dark",
+    "enum": [
+      "dark",
+      "light"
+    ],
+    "type": "string"
+  }
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds 'Read-shaped tools only (anything that buys, sells or writes refuses),' which reinforces but does not exceed the annotations. It also mentions data 'comes back as it is,' which is vague and does not add significant behavioral detail beyond what annotations provide.

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 description is front-loaded with the core purpose and trigger, but includes some fluff such as 'HIGH QUALITY' in caps and branding sentences ('Reso — Orbitx's MCP server...') that are not essential for tool selection. It is somewhat verbose but structured logically.

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?

For a tool with no output schema, the description implies the output is an embeddable chart for chat, and the iframe parameter in the schema clarifies the HTML iframe behavior. It covers the main use case and trigger, though it could explicitly state the return format. Overall, it is fairly complete for a chart tool.

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 86%, so parameters are well-documented in the schema. The description only references CA/mint in the trigger, adding no extra meaning beyond the schema's parameter descriptions. With high coverage, the baseline of 3 is appropriate.

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 provides a DexScreener embed chart for chat, and explicitly lists trigger phrases (chart, graph, DexScreener, candles). It distinguishes itself from sibling tools like orbitx_get_chart by specifying the 'embed for chat' use case, 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 Guidelines4/5

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

The description gives an explicit when-to-call instruction: 'When the user shares a CA/mint and asks for a chart, graph, DexScreener, or candles — call this immediately.' This provides clear context for usage, though it does not mention alternatives or exclusions beyond the trigger.

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