cucm-emulator-mcp

emu_bootstrap_lab

Generate a canonical lab fixture and bootstrap a Cisco CUCM emulator, providing a realistic environment for telephony operations, call simulation, and routing policy testing.

Instructions

Bootstrap the emulator with a generated canonical lab fixture

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

Input Schema

Name	Required	Description	Default
`seed`	No
`locale`	No
`version`	No
`nodeCount`	No
`userCount`	No
`localeMode`	No
`phoneCount`	No
`fixtureName`	No
`phoneIpBase`	No
`neighborMode`	No
`neighborProtocol`	No
`registeredPercent`	No
`userAssociationPercent`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 23, 2026

TDQS

C2.4/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. It does not state whether the operation is destructive (e.g., resets existing state), requires prerequisites, or has side effects on the emulator's current configuration. The single sentence gives no insight into these critical behaviors.

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

Conciseness3/5

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

The description is extremely concise—a single sentence. While it is short, it is under-specified rather than appropriately sized for the tool's complexity. The sentence does state the core action, but it omits essential details, so it does not fully 'earn its place' given the parameter count.

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

Completeness1/5

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

For a tool with 13 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to explain prerequisites, return values, side effects, or parameter semantics. An agent would have no reliable basis for constructing a valid call or understanding the consequences.

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 makes no mention of any of the 13 parameters. It does not explain what parameters like 'seed', 'locale', or 'neighborMode' control, leaving the agent to guess from names alone. The description adds zero value for parameter understanding.

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 states a specific action ('Bootstrap the emulator') with a clear object ('a generated canonical lab fixture'). It distinguishes conceptually from sibling tools like emu_seed_fixtures (which likely seeds data into an existing emulator) by implying initialization, but it does not explicitly name alternatives or contrast behaviors.

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 on when to use this tool versus siblings. Context (e.g., 'for initial setup, use this instead of emu_seed_fixtures') is entirely absent, leaving the agent to infer usage from the name alone.

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

Deploy Server