zandronum-mcp

by rc4l

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List running ACS scripts

list_running_scripts

Check which ACS scripts are currently running and their states by querying Zandronum's scriptstat command.

Instructions

Run scriptstat and return the currently running ACS scripts and their states.

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": "list_running_scripts"
  }
}

Input Schema

Name	Required	Description	Default
`instance`	No

Output Schema

Name	Required	Description	Default
`scripts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 26, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses that the tool runs an external command ('scriptstat'), implying it may execute actions. However, it does not explain side effects, permissions needed, or behavior when no scripts are running. Adequate but not thorough.

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?

Single sentence, no redundancy. However, it could be slightly more informative without sacrificing conciseness.

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?

While output schema exists, the description omits explanation of the parameter and does not elaborate on what 'states' means. Missing critical context for correct invocation.

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 coverage is 0%, and the description does not mention the 'instance' parameter at all. The agent is left to guess its purpose and format with zero guidance.

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 verb ('Run `scriptstat` and return') and the resource ('currently running ACS scripts and their states'). It distinguishes from sibling 'list_scripts' by specifying 'running', making the purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives like 'list_scripts'. The description does not mention contexts, prerequisites, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.