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

cucm-emulator-mcp

by calltelemetry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emu_list_call_sessions

List canonical v2 call sessions to retrieve active call records from the CUCM emulator, enabling monitoring and analysis of telephony operations.

Instructions

List canonical v2 call sessions

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.1/5.0
Behavior1/5

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

The tool likely performs a read-only list operation, but the description does not confirm this or mention any side effects. It does not specify the output format, whether pagination is supported, or if the list is ordered or filtered.

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 concise, consisting of a single phrase, which is efficient. However, it lacks any structural detail such as sections or additional explanatory sentences, making it feel sparse.

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?

Given the simple tool with one parameter, the description is insufficiently complete. It omits information about the output schema, any constraints on the limit parameter, and the meaning of 'canonical', leaving a user with questions.

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?

The schema defines a 'limit' parameter, but the description does not explain its meaning or effect. Without additional context, it is unclear if limit restricts the number of results or serves another purpose.

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 clear action (List) and resource (call sessions), but the term 'canonical' is ambiguous and could confuse users about which sessions are included. It distinguishes from other call session operations like create and get, but not from other list tools like emu_list_active_calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool over alternatives, such as emu_list_active_calls or other listing tools. There is no mention of typical use cases, filtering, or prerequisites.

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