Skip to main content
Glama

MCP Tool-Poisoning, Prompt-Injection & 2026 EU AI Act Auditor MCP

Optimize AI Compute & Robotics Fleet Dispatch Across Global Power Grids

optimize_compute_energy_grid_dispatch
Read-onlyIdempotent

Ranks 6 global datacenter and robotics charging grids (ERCOT, PJM, CAISO, Frankfurt, UK, Seoul) by live solar/wind surplus, cooling PUE, and power cost.

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": "optimize_compute_energy_grid_dispatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoRun duration in hours (default 4)
workloadKwNoCompute or fleet charging load in kW (default 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds some value by naming the six grids and the ranking signals, and "live" hints at real-time external data, but it never states what the call returns, whether the ranking is stable, or what happens with the defaults.

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?

A single front-loaded sentence with zero filler; the grid list and ranking criteria are the most useful details and appear immediately. Slightly dense but nothing is wasted.

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

Completeness3/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 describe the shape of the result — an ordered list of grids with scores? a single recommended grid? — and it does not. For a ranking tool that reads live external data, that omission leaves an agent unsure what to expect back, though the input side is fully covered.

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% and both parameters (hours, workloadKw) carry inline descriptions with defaults, so the schema already does the explanatory work. The description mentions nothing about how the duration or load affect the ranking, so it adds no meaning beyond the schema — baseline 3.

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 gives a concrete verb ("ranks") and a concrete resource (six named grids: ERCOT, PJM, CAISO, Frankfurt, UK, Seoul), plus the ranking criteria (solar/wind surplus, cooling PUE, power cost). It is clear what the tool does, though the name and title promise "optimize ... dispatch" while the description only ranks, leaving a small ambiguity about whether any dispatch action occurs.

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?

There is no guidance on when to use this versus anything else, no prerequisites (e.g. does it need live market feeds or credentials?), and no exclusions. The listed siblings are unrelated domains, so no real routing conflict exists, but the description still offers no usage framing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.