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

cucm-emulator-mcp

by calltelemetry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emu_get_cdr_publisher

Retrieve the canonical configuration and pending state of a CDR publisher within a Cisco CUCM emulator to inspect current and queued settings for call detail records.

Instructions

Get canonical CDR publisher configuration and pending state

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_get_cdr_publisher"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool fetches 'canonical CDR publisher configuration and pending state,' but gives no detail on side effects, authorization needs, or what 'pending state' means. The term 'canonical' is unexplained and there is no note on whether this is a safe read-only operation.

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?

A single, front-loaded sentence that names the resource and the two pieces of data it retrieves. No filler, easy to parse.

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

Completeness3/5

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

For a get-with-no-params tool this is mostly fine, but it never says when to prefer this over emu_get_cdr_history or emu_generate_cdrs, and 'pending state' is undefined. An agent cannot tell what the output looks like or what distinguishes this from siblings.

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

Parameters4/5

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

The tool has zero parameters (schema coverage 100% vacuously), so there is nothing for the description to clarify. Baseline 4 applies.

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 verb (

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 vs alternatives. Among many get_* siblings, there is no mention of which case this one fits or any exclusion criteria. The agent must 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