Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS

tls_reload

Reload TLS domains in OpenSIPS to apply updated certificate configurations without server restart.

Instructions

Reload TLS domains in OpenSIPS via MI command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'tls_reload'. It executes the tls_reload MI command on OpenSIPS via the MI client, returning success/failure. Decorated with @mcp.tool(), @audited('tls_reload'), and @require_permission('mi.write').
    @mcp.tool()
    @audited("tls_reload")
    @require_permission("mi.write")
    async def tls_reload(ctx: Context) -> dict[str, Any]:
        """Reload TLS domains in OpenSIPS via MI command."""
        app = ctx.request_context.lifespan_context
        try:
            result = await app.mi_client.execute("tls_reload")
            return {"reloaded": True, "result": result}
        except Exception as exc:
            logger.warning("tls_reload failed: %s", exc)
            return {"reloaded": False, "error": str(exc)}
  • The docstring describes the tool's purpose ('Reload TLS domains in OpenSIPS via MI command'). The function accepts a Context (no additional parameters) and returns a dict with 'reloaded' and 'result' or 'error' keys.
    """Reload TLS domains in OpenSIPS via MI command."""
    app = ctx.request_context.lifespan_context
    try:
        result = await app.mi_client.execute("tls_reload")
        return {"reloaded": True, "result": result}
    except Exception as exc:
        logger.warning("tls_reload failed: %s", exc)
        return {"reloaded": False, "error": str(exc)}
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on the async function tls_reload. The module is imported in server.py line 206 to activate the registration.
    @mcp.tool()
    @audited("tls_reload")
    @require_permission("mi.write")
    async def tls_reload(ctx: Context) -> dict[str, Any]:
        """Reload TLS domains in OpenSIPS via MI command."""
        app = ctx.request_context.lifespan_context
        try:
            result = await app.mi_client.execute("tls_reload")
            return {"reloaded": True, "result": result}
        except Exception as exc:
            logger.warning("tls_reload failed: %s", exc)
            return {"reloaded": False, "error": str(exc)}
  • The tool name 'tls_reload' is also referenced in the reload_data_tables tool's target list, mapped to module 'tls_mgm', allowing batch reload of TLS along with other modules.
        ("tls_reload", "tls_mgm"),
    ]
  • MI command registration for tls_reload, describing it as 'Reload TLS domains from database', associated with module 'tls_mgm', permission 'mi.write', category 'tls_mgm'.
    _r("tls_reload", "tls_mgm", "Reload TLS domains from database", permission="mi.write", category="tls_mgm")
    _r("tls_list", "tls_mgm", "List configured TLS domains", category="tls_mgm")
    _r("tls_info", "tls_mgm", "Show TLS domain configuration details", category="tls_mgm")
    _r("tls_trace", "tls_mgm", "Enable or disable TLS tracing", ["mode"], "mi.write", "tls_mgm")
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 disclosing behavior. It only says 'reload,' which implies a potentially state-changing operation, but does not clarify side effects (e.g., whether existing connections are dropped, if certificates are re-read), permissions needed, or whether it is non-disruptive.

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 of 8 words, perfectly concise and front-loaded with the verb. No wasted words.

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?

Given no parameters and the presence of an output schema, the description provides sufficient context for a simple reload command. However, it lacks information about the output (though schema covers that) and could elaborate on what 'reload' entails (e.g., effect on current TLS sessions).

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 no parameters, and schema coverage is 100%. The description adds no parameter details, which is appropriate given the absence of parameters. Baseline for 0 parameters is 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 action (reload) and resource (TLS domains), and context (OpenSIPS via MI command). It effectively distinguishes itself from sibling tools like tls_add, tls_delete, tls_list, and tls_update by focusing on the reload operation.

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 versus alternatives, nor any prerequisites or context. The description simply states what it does without explaining scenarios (e.g., after configuration changes) or when not to use it.

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