Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cheat_list

Lists available cheat and debug bridge methods with their arguments so clients can select valid debug actions; requires a write lease and session ID.

Instructions

List the available cheat/debug bridge methods and their arguments. 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_list"
  }
}

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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key auth requirement of needing the write lease. It also indicates the return content is a list of methods and arguments, but it omits whether the operation is strictly read-only, how errors are reported, and any rate-limit or side-effect details.

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 compact sentences with no wasted wording. The core purpose is front-loaded, and the prerequisite follows immediately.

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 listing tool with no output schema, the description states the core purpose, the required write lease, and the kind of data returned. It could be more complete about output format and usage alternatives, but it contains enough to select and invoke the tool correctly.

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 lease and session_id are already documented in the input schema. The description reinforces that the lease is specifically the write lease, but adds no meaning for session_id and no formatting or retrieval semantics beyond the schema baseline.

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 uses a specific verb, "List", and a clear resource, "available cheat/debug bridge methods and their arguments". It is easy to distinguish from cheat action siblings like cheat_complete_mission, though it does not explicitly differentiate itself from related discovery tools such as bridge_probe.

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?

It provides an important prerequisite, "Requires the write lease", which tells the agent when it is eligible to call the tool. However, it does not explicitly say when to use this versus bridge_probe or other discovery tools, so the guidance is only implied by the purpose.

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