Skip to main content
Glama
Sign In
mcp-ocei-oracle

mcp-ocei-oracle

by Mr-Didi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

evaluate_orbital_compute_regime

Evaluate orbital versus terrestrial AI compute economics and physics before scheduling batch training or inference. Computes OCEI scores, eclipse and thermal limits, SEU checkpointing, and $/MTok TCO.

Instructions

Invoke before scheduling batch AI training/inference or evaluating orbital vs. terrestrial compute TCO. Computes OCEI v2.2 Spot/Structural/TWAP scores, L1 shockwave lead time, beta-angle eclipse battery mass, Earth IR/albedo radiator sizing, Silicon Tj throttling, Young-Daly SEU checkpointing, and $/MTok unit economics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "evaluate_orbital_compute_regime"
  }
}

Input Schema

NameRequiredDescriptionDefault
hwNorubin_nvl72
beta_degNoSolar beta angle in degrees.
power_mwNoTarget cluster IT power in MW.
storm_modeNolive
altitude_kmNoOrbital altitude in km.
loop_temp_cNoRadiator liquid coolant loop temperature in C.
grid_price_usd_mwhNoTerrestrial electricity price in $/MWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Computes' implies a calculation, but the description does not explicitly state that the tool is read-only/non-mutating, deterministic, or free of side effects, nor does it discuss runtime or external dependencies.

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 front-loaded sentence with no filler, starting with invocation guidance before listing computed metrics. The metric list is dense and jargon-heavy, but it remains reasonably concise for a complex evaluator.

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?

This is a 7-parameter complex model with no annotations and no output schema. The description lists computed metrics but does not explain the return structure, how to interpret the scores, or the meaning of defaults and enum choices, leaving significant gaps for correct use.

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 71%, so the schema already documents most parameters. The description mentions domain concepts like beta-angle, radiator sizing, and SEU checkpointing, but it does not map them to specific inputs such as hw, storm_mode, power_mw, altitude_km, loop_temp_c, or grid_price_usd_mwh.

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 states a specific verb, 'Computes', and names the resource: OCEI v2.2 scores, orbital vs. terrestrial TCO, and related engineering metrics. It does not explicitly contrast with siblings, but the evaluator framing is clear enough to distinguish it from dispatch or allocation 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 says to invoke the tool 'before scheduling batch AI training/inference or evaluating orbital vs. terrestrial compute TCO,' giving two concrete usage scenarios. It does not state when not to use it or name alternative tools, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools