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. Resolves the best liquidity pair and returns markdown with live embed URL, iframe, price/liq/volume stats, interval links, and OrbitX trade link. Works with Solana mint CA or pair address (also EVM).

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). 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.
intervalNoChart timeframe for the embed15m

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. 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"
+  }
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already known. The description adds meaningful behavioral context: it resolves the best liquidity pair, returns markdown with specific components, and works across Solana and EVM. It doesn't mention rate limits or failure modes, but for a read-only chart tool the added context is sufficient.

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

Conciseness4/5

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

The description is a single dense paragraph that front-loads the trigger condition and core value proposition. Every sentence earns its place, though the authCode explanation is long and arguably belongs in the schema (it's already there). Slight redundancy with the schema's authCode description prevents a 5.

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 read-only chart tool with no output schema, the description covers the trigger, input types, output contents, and chain support. It doesn't explain what happens when the pair can't be resolved or how errors surface, but the annotations (readOnlyHint, openWorldHint) and high schema coverage mean the agent has enough to call it correctly. A 5 would require explicit failure/fallback behavior.

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 the schema already documents most parameters. The description adds context for 'ca' (token contract address or pair address) and 'mint' (alias of ca), which is helpful. However, it doesn't add meaning beyond the schema for chain, theme, iframe, interval, or authCode. Baseline 3 is appropriate given high schema coverage.

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 states a specific verb ('call this immediately'), resource ('DexScreener embed chart'), and output ('markdown with live embed URL, iframe, price/liq/volume stats, interval links, and OrbitX trade link'). It also distinguishes from siblings by naming the trigger condition (user shares CA/mint and asks for chart/graph/DexScreener/candles).

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

Usage Guidelines5/5

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

Explicitly says when to call ('When the user shares a CA/mint and asks for a chart, graph, DexScreener, or candles — call this immediately'). It also clarifies scope ('Works with Solana mint CA or pair address (also EVM)'), which helps the agent decide applicability. It doesn't name a specific alternative tool, but the trigger condition is so specific that it effectively routes the agent.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources