Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cheat_refill_ammo

Restore ammunition for all weapons carried by the player's squads. Use it to top up squad magazines during combat or after scavenging, with a valid write lease and session ID.

Instructions

Refill the ammunition of every weapon carried by the player's squads. Requires the write lease.

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": {
      "lease": "<lease>",
      "session_id": "<session_id>"
    },
    "name": "cheat_refill_ammo"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
session_idYesCurrent session_id from get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose the authorization requirement (write lease) and that the effect is a mass, all-squads refill. It does not describe whether the operation is idempotent, what state it mutates beyond ammo counts, whether it fails partially, or what it returns, leaving meaningful gaps for a state-mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste: the action and its scope come first, and the authorization prerequisite follows immediately. Nothing is repeated or padding.

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?

For a simple two-parameter cheat tool with a fully described schema, the description covers what it does and the lease prerequisite adequately. The absence of annotations and of an output schema means return behavior and side effects are unexplained, which leaves it only minimally complete for a mutating tool.

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 coverage is 100% and both parameters are documented there, including where the lease and session_id come from. The description only echoes the lease requirement and adds no syntax, format, or validation detail beyond the schema, so the baseline 3 applies.

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 and resource ('Refill the ammunition') with a precise scope ('every weapon carried by the player's squads'), which implicitly separates it from the per-member sibling refill_squad_member_ammo. It stops short of naming that sibling, so an agent must infer the distinction from scope wording alone.

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?

The prerequisite ('Requires the write lease') is explicit and useful context for when this call can succeed. However, there is no explicit when-not guidance and no named alternative, even though refill_squad_member_ammo is clearly the narrower option an agent may need to choose against.

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

Deploy Server

Other Tools