Skip to main content
Glama
Diogenes EVE: Frontier Sui Move & Smart Assembly MCP

Diogenes EVE: Frontier Sui Move & Smart Assembly MCP

EVE Frontier Lagrange Network Node Gigajoule & Fuel Burn Optimizer

optimize_eve_node_power
Read-onlyIdempotent

Calculate Lagrange Network Node hourly gigajoule fuel burn, capacity headroom, and offline vulnerability windows for connected Smart Assemblies to balance steady-state power allocations.

Instructions

Calculates Lagrange Network Node hourly gigajoule (GJ) fuel burn rates, capacity headroom, and offline vulnerability windows for connected Smart Assemblies. Use when balancing steady-state power allocations on a single Lagrange Network Node; for stress-testing node capacitor depletion under active hostile fleet bombardment, use simulate_eve_capacitor_siege instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'node_id' ('operating_profile' defaults to 'balanced'), supports '?demo=true' or L402 (100 sats), and returns HTTP 400 if invalid.

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": {
      "node_id": "<node_id>"
    },
    "name": "optimize_eve_node_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYesLagrange Network Node identifier (e.g. 'node-frontier-01').
operating_profileNoPower allocation profile across connected assemblies; defaults to 'balanced' when omitted.

Output Schema

NameRequiredDescriptionDefault
node_idYesEvaluated Lagrange Network Node identifier.
burn_rate_gj_per_hrYesHourly gigajoule (GJ) energy consumption across attached assemblies.
hours_until_fuel_depletionYesRemaining operational hours before fuel reserves reach zero.
offline_threat_window_hoursYesSafety classification ('SAFE' or 'CRITICAL_OFFLINE_IMMINENT').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context they do not carry: stateless edge call, 32 KB payload cap, 60 RPM rate limit, auth via '?demo=true' or L402 (100 sats), and HTTP 400 on invalid input. These are exactly the operational traits an agent needs before invoking.

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 purpose and the sibling routing come first, followed by operational constraints in a compact single-sentence block. It is dense but front-loaded and wastes little; only the parenthetical constraint run borders on over-packing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers purpose, alternative routing, auth, limits, and error behavior. Nothing material for a correct call is missing.

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 100%, so both parameters (including the enum values and the 'balanced' default) are already documented. The description restates node_id and the operating_profile default without adding format, constraint, or edge-case meaning beyond the schema, which lands at the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (calculates) plus the exact resource and outputs: hourly GJ fuel burn, capacity headroom, offline vulnerability windows for connected Smart Assemblies. It also explicitly distinguishes itself from simulate_eve_capacitor_siege, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives a positive use case ('balancing steady-state power allocations on a single Lagrange Network Node') and names the alternative tool with the condition that selects it ('stress-testing node capacitor depletion under active hostile fleet bombardment'). When-to-use and when-not-to-use are both explicit.

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