Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

orbitx_menu · Orbitx

orbitx__orbitx_menu
Read-only

OrbitX command menu — branded banner + capability list. Call when the user says /, menu, help, or asks what you can do.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authCodeNoOptional authCode from dashboard paste or orbitx_auth_link

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": "Optional authCode from dashboard paste or orbitx_auth_link",
+    "type": "string"
+  }
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by stating the menu is a branded banner plus capability list, and nothing in the description contradicts 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.

Conciseness5/5

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

The description is a single sentence that front-loads what the tool is and then gives concrete trigger phrases. Every phrase earns its place and there is no redundant filler.

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 simple, read-only menu tool with no required parameters and a fully documented optional authCode, the description covers the main behavior and invocation triggers. It could explain how authCode affects the menu output, but the schema already covers the parameter's origin.

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?

The only parameter, authCode, is fully described in the input schema, so schema coverage is 100%. The description itself adds no parameter-level meaning, leaving the baseline score of 3 appropriate.

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 the OrbitX command menu and clarifies its output as a branded banner plus capability list. Although it lacks an explicit verb like 'displays' or 'lists', the purpose is unmistakable and distinct from the many data-focused OrbitX sibling tools.

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?

It explicitly states when to call: when the user types /, says menu or help, or asks what the agent can do. It does not mention when not to call or name an alternative, but for a menu/help tool the trigger conditions are clear enough.

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