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

cucm-emulator-mcp

by calltelemetry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emu_get_call_session

Retrieve a call session by its ID to access the canonical v2 session data from the CUCM emulator.

Instructions

Get a canonical v2 call session

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": {
      "id": "<id>"
    },
    "name": "emu_get_call_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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 carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not explain error behavior, required state, edge cases, or what 'canonical v2' means regarding the returned data. It provides minimal transparency for an unannotated tool.

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 short sentence with no wasted words, and it communicates the core action. Its brevity is not a structural problem, though it contributes to under-specification in other dimensions.

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?

For a tool with one required parameter, no output schema, no annotations, and a large sibling set, this description is too thin. It lacks information about what 'canonical' denotes, what the 'id' refers to, and how this retrieval tool is used in workflows alongside the other session tools.

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 does not mention the required 'id' parameter at all. The schema only provides a type of 'string', leaving the agent without any explanation of which identifier is expected, its format, or how to obtain it. The description adds no semantic value beyond the parameter name.

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 ('Get') and a specific resource ('a canonical v2 call session'), which distinguishes it from creating, listing, or modifying call sessions. However, 'canonical' is not explained, leaving some ambiguity about what exactly is returned.

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?

There is no guidance about when to use this tool instead of siblings such as emu_list_call_sessions or emu_create_call_session. The name implies retrieval of an existing session, but the description does not clarify the intended context or exclusions.

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