Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS

cc_list_queue

List all calls currently queued in the call center to monitor and manage call flow.

Instructions

List all calls currently queued in the call center.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the cc_list_queue MCP tool. Decorated with @mcp.tool() and @require_permission('mi.read'). It retrieves the lifespan context and executes the 'cc_list_queue' MI command via the MI client.
    @mcp.tool()
    @require_permission("mi.read")
    async def cc_list_queue(ctx: Context) -> dict[str, Any]:
        """List all calls currently queued in the call center."""
        app = ctx.request_context.lifespan_context
        result = await app.mi_client.execute("cc_list_queue")
        return result
  • Registration of cc_list_queue as a known MI command in the MI_COMMANDS registry. Declares it belongs to the 'call_center' module with 'mi.read' permission.
    _r("cc_list_queue", "call_center", "List queued calls", category="call_center")
  • The cc_status tool uses cc_list_queue internally as a helper to fetch queue data as part of a combined call center status response.
    @mcp.tool()
    @require_permission("mi.read")
    async def cc_status(ctx: Context) -> dict[str, Any]:
        """Get a combined call center status: queue, agents, and flows.
    
        Returns all three datasets in a single response for a complete
        overview of the call center state.
        """
        app = ctx.request_context.lifespan_context
        queue = await app.mi_client.execute("cc_list_queue")
        agents = await app.mi_client.execute("cc_list_agents")
        flows = await app.mi_client.execute("cc_list_flows")
        return {
            "queue": queue,
            "agents": agents,
            "flows": flows,
        }
Behavior3/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 truthfully states it 'lists' calls, implying a read operation, but does not mention permissions, side effects, or performance characteristics.

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, concise sentence of 10 words, front-loading the core purpose with no extraneous information.

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

Completeness4/5

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

Given the simple nature of the tool (list all queued calls) and the presence of an output schema, the description is adequate. However, it could provide more context, such as what 'queued' means or if the list is ordered.

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?

There are zero parameters, so schema coverage is 100%. The description does not need to add parameter information, earning a baseline of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: listing all calls currently queued in the call center. The verb 'List' and resource 'calls queued' are specific, and it distinguishes from sibling tools like 'cc_list_agents' and 'cc_status'.

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

Usage Guidelines3/5

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

The description implies usage for viewing queued calls but provides no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OpenSIPS/opensips-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server