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. — 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
limitNo
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. 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"
+  }
+}
  2. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, but the description adds useful behavioral context: the tool is 'read-shaped,' any write operation refuses, and data is returned unmodified ('their data comes back as it is'). This goes beyond annotations, though it omits pagination or response format details.

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 core purpose is front-loaded in the first clause, but the middle segment about Orbitx's MCP server and 'a live seat on The Wall' is server-level context rather than tool behavior. The listing URL is auxiliary. The description is not bloated, yet not every sentence earns its place.

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?

With no output schema, the description should explain what the tool returns and any operational details like pagination or limit behavior. It only says 'labels and performance,' leaving the return shape unclear. It also omits when to use this over sibling tools, so the description is only minimally adequate for a simple read-only directory tool.

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 description adds no meaning for the 'limit' or 'authCode' parameters. Schema coverage is only 50% because 'limit' lacks a description, and the tool description does not compensate. 'limit' is somewhat inferable from its name and default, but the description itself contributes nothing about either parameter.

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 identifies the tool as a 'KOL / smart-money directory with labels and performance,' clearly naming the resource it returns and distinguishing it from sibling tools like orbitx_get_signals or orbitx_get_forensics. It lacks an explicit verb like 'list' or 'retrieve,' but the tool name 'get_kols' plus 'directory' makes the intent clear enough.

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 provides no guidance on when to use this tool versus related Orbitx directory/search tools, nor any exclusions or alternative tool names. It only states a broad read-only constraint and server context, which does not help an agent choose this specific tool.

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