Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_scavenge_progress

Track all in-progress scavenges with progress (0–1), time remaining, and counts of loot crates and characters inside to monitor active missions.

Instructions

List every in-progress scavenge: progress 0-1, time left, remaining loot crates and characters inside.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
session_idYesCurrent session_id from get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/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 burden, and it does disclose the shape of the returned data (progress normalized 0-1, time left, crates, occupants). It does not state that it is a read-only operation, whether results are scoped to the required session_id or global, or how the limit parameter truncates results.

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?

A single front-loaded sentence that enumerates exactly what is returned with no filler. Every clause earns its place by telling the agent what fields to expect.

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 two-parameter read tool with no output schema and no annotations, the description does a decent job of covering the return payload. It falls short on the limit parameter, session scoping, and any indication of ordering or empty-result behavior.

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 coverage is 50%: session_id is documented in the schema ('Current session_id from get_state'), but limit is entirely undocumented. The description adds no parameter meaning at all — it never mentions session scoping or the 1-200 limit, so the undocumented parameter is left ambiguous.

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 ('List') and resource ('in-progress scavenge') and enumerates the returned fields (progress 0-1, time left, remaining loot crates, characters inside). The 'in-progress' qualifier implicitly separates it from the sibling get_scavenge_plan, but no sibling is named explicitly.

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?

Usage is only implied: 'in-progress scavenge' tells the agent this reports live runs rather than plans. There is no explicit statement of when to prefer this over get_scavenge_plan or get_loot_targets, and no stated prerequisites.

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