Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS

b2b_sca_list

List all active Shared Call Appearance (SCA) subscriptions to monitor B2B shared line states and manage telephony resources.

Instructions

List active Shared Call Appearance (SCA) subscriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the b2b_sca_list MI command. It is decorated with @mcp.tool() to expose it as an MCP tool and @require_permission('mi.read') for RBAC. Calls app.mi_client.execute('b2b_sca_list') to run the OpenSIPS MI command.
    @mcp.tool()
    @require_permission("mi.read")
    async def b2b_sca_list(ctx: Context) -> dict[str, Any]:
        """List active Shared Call Appearance (SCA) subscriptions."""
        app = ctx.request_context.lifespan_context
        return await app.mi_client.execute("b2b_sca_list")
  • Registration entry for the 'b2b_sca_list' MI command via the _r() helper, describing it as belonging to the 'b2b_sca' module with 'List SCA subscriptions' description and default 'mi.read' permission.
    _r("b2b_sca_list", "b2b_sca", "List SCA (Shared Call Appearance) subscriptions", category="b2b_sca")
  • The _r() helper function used to register MI commands into the MI_COMMANDS registry. It creates an MICommand dataclass instance and stores it in the global dictionary.
    def _r(
        name: str,
        module: str,
        desc: str,
        params: list[str] | None = None,
        permission: str = "mi.read",
        category: str = "core",
    ) -> None:
        MI_COMMANDS[name] = MICommand(name, module, desc, params or [], permission, category)
Behavior3/5

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

The description implies a read-only, non-destructive action, but no explicit behavioral traits are disclosed beyond that. With no annotations, the description is minimally adequate for a simple list 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?

The description is a single sentence with no redundant information. It is concise and front-loaded.

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 tool has no parameters and likely returns a list of subscriptions (output schema exists), the description is brief but covers the essential functionality. It is complete for a straightforward list tool.

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 input schema has no parameters, so the description adds no parameter-specific information. According to the baseline for 0 parameters, this is sufficient.

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 specifies the verb 'List' and the resource 'active Shared Call Appearance (SCA) subscriptions'. It is specific and distinguishes this tool from siblings like b2b_bridge or b2b_list_entities.

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. It does not mention related operations or conditions that would warrant its use.

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