Skip to main content
Glama
Sign In
zandronum-mcp

zandronum-mcp

by rc4l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect aimed target

inspect_target

Run linetarget to get the actor a player is aiming at, including class, health, and spawn health.

Instructions

Run linetarget and return the actor the player is aiming at (class, health, spawn health).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It mentions running 'linetarget' but does not clarify if this is read-only, if it can fail (e.g., no target), or any side effects. The agent lacks information about safety or state impact.

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

Conciseness4/5

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

The description is a single, direct sentence that states the command and return fields. It is efficient and front-loaded, but slightly too brief given the lack of parameter explanation.

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?

The tool is simple but the description omits important details: parameter meaning, error handling, and output format. Without an output schema, more context about the returned data structure would be valuable.

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?

The only parameter 'instance' is not described in the tool description. Schema coverage is 0%, so the agent has no explanation of what 'instance' refers to (e.g., game instance number, player instance). This is a critical gap.

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 clearly states the tool runs 'linetarget' and returns the aimed actor's class, health, and spawn health. It is specific about the resource and action, and distinguishes from siblings like 'actors_near' which lists nearby actors rather than the current target.

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 on when to use this tool versus alternatives (e.g., 'actors_near', 'actor_state'). No prerequisites, error conditions, or context hints are provided, leaving the agent to infer when this tool is appropriate.

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