Skip to main content
Glama
Pyrogenesis Fair Player MCP

Pyrogenesis Fair Player MCP

by yunqinglt

cancel_production

Cancel a queued training or research item in a completed building by specifying its queue ID from observe_player; normal refunds apply and a training batch is removed as a whole.

Instructions

Cancel a current training/research queue item in your completed building.

Use the production.queue item's id from observe_player. Normal engine refunds apply; a training batch is removed as a whole. Observe again if the queue changed meanwhile.

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": {
      "building_id": "<building_id>",
      "queue_id": "<queue_id>"
    },
    "name": "cancel_production"
  }
}

Input Schema

NameRequiredDescriptionDefault
queue_idYes
building_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that normal engine refunds apply, that a training batch is removed as a whole, and that stale queue state is a risk requiring re-observation. It omits failure behavior (invalid queue_id, incomplete building) and any permission or return-value expectations.

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?

Three short sentences, front-loaded with the core action, then the id source, then side effects and the staleness caveat. Nothing is redundant, though the paragraph could be tightened into a single structured block.

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 two-parameter mutation with no output schema and no annotations, the description covers side effects, atomicity, id provenance, and staleness. The remaining gap is error/edge-case behavior and fuller building_id semantics.

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 0%, so the description must compensate. It clearly explains queue_id's origin and meaning (the production.queue item id from observe_player), but building_id is only implicitly framed as 'your completed building' with no detail on whether it must be fully constructed.

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?

States a specific verb (cancel) and a specific resource (a training/research queue item in a completed building), so the agent knows exactly what is removed and where. It does not explicitly contrast with sibling cancel tools such as cancel_unit_packing, so sibling differentiation is only implicit in the resource scope.

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?

Gives concrete preconditions and provenance: the queue_id must come from observe_player's production queue, and the agent is told to re-observe if the queue changed. It stops short of naming alternatives or stating when not to use this tool (e.g., cancelling unit packing).

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