Skip to main content
Glama
Pyrogenesis Fair Player MCP

Pyrogenesis Fair Player MCP

by yunqinglt

leave_turret

Orders ejectable occupants to leave turret positions using the native command; use unload_garrison for garrison occupants instead.

Instructions

Order your ejectable occupants to leave turret positions using the native command.

Garrison occupants use unload_garrison instead. The game revalidates actual turret occupancy and ejection permissions; fixed non-ejectable turret occupants are refused.

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": {
      "entity_ids": "<entity_ids>"
    },
    "name": "leave_turret"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does meaningful work: it discloses that the native command is used, that the game revalidates actual turret occupancy and ejection permissions server-side, and that fixed non-ejectable occupants are rejected. It does not describe what happens to units after they leave the turret or whether the order can fail for other reasons, leaving some behavioral surface undisclosed.

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 action, then the alternative, then the failure behavior. No filler, though the sentence fragments around 'using the native command' and the line-broken formatting are slightly choppy.

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 one-parameter action tool with no output schema and no annotations, the description covers purpose, sibling routing, and server-side validation behavior. It is only incomplete on what entity_ids refers to, which is a real but single omission.

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% and the single parameter entity_ids is never explained. It is genuinely ambiguous whether these are turret entity ids, occupant entity ids, or both, and the description's phrase 'your ejectable occupants' does not resolve it. This is the clearest gap in the definition.

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 and resource: ordering ejectable occupants to leave turret positions, and explicitly names the sibling case (garrison occupants) that this tool does not cover. An agent can distinguish it from unload_garrison 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 Guidelines4/5

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

Explicitly routes garrison occupants to unload_garrison, which is a concrete when-not condition, and notes that non-ejectable fixed occupants are refused. It does not state any positive preconditions (e.g., which entity_ids to pass, ownership requirements), so it stops short of full when/when-not coverage.

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