Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

take_vehicle

Order a walking squad to reach a discovered abandoned vehicle and take it over; the squad boards it, and you can read squads and vehicles to confirm the owner change.

Instructions

Order a walking squad to reach a discovered abandoned vehicle and take it over. The squad walks there and boards natively; read squads and vehicles afterwards to confirm the owner change.

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>",
      "request_id": "<request_id>",
      "squad_id": "<squad_id>",
      "vehicle_id": "<vehicle_id>"
    },
    "name": "take_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
squad_idYes
request_idYes
session_idYesCurrent session_id from get_state
vehicle_idYes
replace_ordersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that the squad travels on foot ('walks there'), becomes the new owner ('take it over'), and that the outcome should be verified afterwards via squad and vehicle reads. What it leaves out is failure behavior — whether the call blocks until arrival, what happens if the journey is interrupted, and how errors are surfaced.

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 sentences, no wasted clauses. The action is front-loaded in the first sentence and the verification advice follows immediately, which is the right information order for an agent about to call it.

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 six-parameter mutation tool with zero annotations and no output schema, the description explains the mechanic and the follow-up check but not the control-flow prerequisites (lease acquisition) or the meaning of replace_orders. It is adequate to understand what the tool does, incomplete for calling it correctly.

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 only 33%, and the description names only the entities behind squad_id and vehicle_id. The lease token, session_id, and request_id are never mentioned, and replace_orders is a completely undocumented boolean whose effect on existing orders is exactly the kind of ambiguity that changes agent behavior.

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?

The description gives a specific verb-and-resource pair: a walking squad is ordered to reach a discovered abandoned vehicle and take it over. This is clearly distinct from the read-only siblings (get_vehicle_hunt, get_vehicle_map), and an agent can identify the tool's job without opening its schema.

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?

Preconditions are implied by 'walking squad' and 'discovered abandoned vehicle', which tells the agent to look something up first, but neither is stated as a hard requirement. There is no statement of when not to use this, what to do if the vehicle is no longer abandoned, or which sibling to prefer for the reconnaissance step.

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