mcp-ocei-oracle

compute_arbitrage_dispatch

Evaluates real-time spot electricity prices against an orbital breakeven threshold and returns a deterministic workload routing directive—ORBIT_PRIMARY, HYBRID_SPLIT, or TERRESTRIAL_PRIMARY.

Instructions

Evaluates real-time spot electricity price ($/MWh) against the orbital breakeven threshold to output a deterministic workload routing directive (ORBIT_PRIMARY, HYBRID_SPLIT, or TERRESTRIAL_PRIMARY).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grid_price_usd_mwh": "<grid_price_usd_mwh>"
    },
    "name": "compute_arbitrage_dispatch"
  }
}

Input Schema

Name	Required	Default
`hw`	No	rubin_nvl72
`power_mw`	No
`storm_mode`	No	live
`grid_price_usd_mwh`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully states that the output is a deterministic routing directive with three possible labels, but it does not clarify whether the tool only computes a recommendation or actually performs dispatch, nor does it describe permissions, side effects, or rate limits.

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 that states the operation, comparison basis, and output categories without filler. It is dense and somewhat jargon-heavy, especially 'orbital breakeven threshold,' but not verbose.

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?

For a four-parameter tool with two enums, no annotations, and no output schema, the description is incomplete. It covers the purpose and output directive labels, but leaves the semantics of three parameters and the output contract beyond those labels unspecified.

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?

Schema description coverage is 0%, so the description needs to explain the four parameters. It gives some meaning for grid_price_usd_mwh as real-time spot electricity price in $/MWh, but completely omits hw, power_mw, and storm_mode, including their enums and defaults.

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 uses a specific verb, 'Evaluates,' and names the core inputs and output: real-time spot electricity price versus an orbital breakeven threshold, producing a workload routing directive. It is clearly about arbitrage dispatch, though it does not explicitly distinguish itself from the sibling tools by name.

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

Usage Guidelines3/5

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

Usage is implied: call this when you need to compare spot grid price against a breakeven threshold and obtain a routing directive. However, the description gives no explicit when-not-to-use guidance and does not name or point to any alternative tool.

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

Deploy Server