Skip to main content
Glama
OpenSIPS

OpenSIPS MCP Server

Official
by OpenSIPS

module_scaffold

Generate a complete OpenSIPS C module skeleton. Creates all necessary files for a new module including C source, header, Makefile, and README. Supports optional MI command and parameter definitions.

Instructions

Generate a complete OpenSIPS C module skeleton.

Creates all necessary files for a new OpenSIPS module: C source, header, Makefile, README, and optional MI command implementations.

Parameters

name: Module name (e.g. my_module). Must be a valid C identifier. description: Short description of the module's purpose. mi_commands_json: JSON array of MI commands. Each element should have name, optional description, and optional params (list of strings). Example: [{"name": "my_cmd", "description": "Does something", "params": ["arg1"]}] params_json: JSON array of module parameters. Each element should have name, type (str or int), and optional default. Example: [{"name": "db_url", "type": "str", "default": "mysql://localhost/opensips"}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
mi_commands_jsonNo[]
params_jsonNo[]

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries full burden. It explains what files are created and optional MI commands, but lacks disclosure on potential overwrites, authorization needs, or error conditions. The behavior is partially transparent but incomplete for a generation tool.

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 concise and well-structured. The first sentence states the core purpose, followed by a list of output files, then a clear 'Parameters' section with bullet points. No wasted sentences, and critical info is 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 that an output schema exists (context signal) and parameters are well-documented, the description is mostly complete. It lacks details on return value and error conditions, but for a generation tool with detailed params, it is adequate. Not perfect, hence 4.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates. It explains each parameter: name must be a valid C identifier, description is short text, mi_commands_json and params_json have clear structure with examples. This adds significant value beyond the bare schema.

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: 'Generate a complete OpenSIPS C module skeleton.' It specifies the exact outputs (C source, header, Makefile, README, optional MI commands) and distinguishes itself from sibling tools by focusing on module creation from scratch.

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 does not explicitly guide when to use this tool vs alternatives. There are sibling tools like module_add_mi_command and module_compile for subsequent steps, but no mention of when to use scaffolding vs those. The context implies it's for new modules, but no when-not-to or alternative references.

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