Skip to main content
Glama
Sign In
cucm-emulator-mcp

cucm-emulator-mcp

by calltelemetry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emu_import_snapshot

Restores a Cisco Unified CM emulator environment by importing a snapshot pack containing call sessions, CDR/CMR records, routing policies, and device configurations.

Instructions

Persist a provided snapshot pack

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": {
      "pack": "<pack>"
    },
    "name": "emu_import_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior1/5

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

There are no annotations and the description provides no information about side effects, whether existing snapshots are overwritten, persistence guarantees, or error behavior. This lack of transparency is critical for a tool that likely modifies stored state.

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, clear sentence with no unnecessary words. It is highly concise and achieves its communicative purpose with minimal text.

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?

Given the complexity of the input schema and the presence of many related snapshot tools, the description is severely incomplete. It does not mention return values, success criteria, potential failures, or whether the operation is destructive. This leaves significant gaps for an agent deciding how to use the tool correctly.

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

Parameters3/5

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

While the input schema is extremely detailed and self-explanatory, the description adds no additional meaning to the 'pack' parameter. Since the schema thoroughly defines the structure, the baseline of 3 is appropriate, but the description does not enhance or clarify parameter semantics further.

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 'Persist a provided snapshot' clearly states the verb (persist) and resource (snapshot), and the tool name aligns with sibling tools like emu_export_snapshot and emu_load_snapshot, making its purpose unambiguous. However, it could be more specific about what 'persist' entails (e.g., save to store, overwrite).

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 alternatives like emu_load_snapshot or emu_export_snapshot. The description does not mention any conditions or scenarios that would indicate its appropriate use, leaving the agent to infer 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

Other Tools