Skip to main content
Glama
Sign In
zandronum-mcp

zandronum-mcp

by rc4l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Give item

give

Adds a specified inventory item to a player in Zandronum. Configure amount and instance for precise item delivery.

Instructions

Give an inventory item to the player.

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": {
      "item": "<item>"
    },
    "name": "give"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
amountNo
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0
  2. Removedv0.4.3
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Give an inventory item to the player.' It does not mention possible side effects, prerequisites, or behavior in different contexts (e.g., menu screens, invalid items).

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?

The description is a single, straightforward sentence with no redundant words. It is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 3 parameters, no annotations, and no output schema, this description is too minimal. It does not explain the role of 'amount' or 'instance', nor does it provide any context about inventory limits, game state requirements, or relationship to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no detail about the 'item', 'amount', or 'instance' parameters. The meaning of 'amount' and 'instance' is entirely undocumented, and 'item' is already self-evident from the schema.

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 clearly states the action (give), the resource (inventory item), and the recipient (the player). This distinguishes it from sibling tools like take and summon, even without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as take or summon. The description only states what it does, leaving the agent to infer appropriate usage.

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