Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_get_kols · Orbitx

orbitx__orbitx_get_kols
Read-only

KOL / smart-money directory with labels and performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
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. Changed2 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"
+  },
+  "limit": {
+    "default": 20,
+    "type": "integer"
+  }
+}
  3. First observed

TDQS

B3/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, so the safety and open-world characteristics are carried by structured metadata. The description adds a modest behavioral hint that results include 'labels and performance,' but it says nothing about sorting, default scope, or data recency. There is no contradiction with the annotations.

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 economical sentence with no filler and puts the core concept ('KOL / smart-money directory') first. It is concise, though the brevity sacrifices operational detail that would have made it more useful.

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?

For a simple read-only list tool with two optional parameters, the basic purpose is present, and authCode is documented in the schema. However, there is no output schema, and 'labels and performance' is vague about the response shape; the description also doesn't mention how many results are returned by default beyond the schema's default value. It is adequate but has clear gaps.

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?

The schema documents authCode in detail but leaves limit with only a default and no textual explanation; the description itself does not explain either parameter. With schema description coverage at only 50%, the description should compensate by explaining what 'limit' controls (e.g., maximum number of KOLs returned), and it does not.

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 identifies the resource as a KOL / smart-money directory and names the kind of data returned ('labels and performance'), so an agent can tell what the tool exposes. It is a noun phrase rather than an explicit verb, and it doesn't directly distinguish itself from sibling tools like orbitx__orbitx_leaderboard or orbitx__orbitx_search.

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?

The description gives no guidance on when to use this tool versus the many other orbitx read tools. There is no mention of alternatives, exclusions, or the kind of query that should route to this directory instead of leaderboard or search.

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