Skip to main content
Glama

Create or retrieve an answering-line SIP address

create_sip_address
Idempotent

Create (first call) or read the SIP address and private trunk credentials for one of the signed-in owner's answering lines, so the owner's phone system can send calls to the line over SIP, with no phone number, instead of forwarding a number. For the line's number and forwarding codes use get_answering_line. Pass the line_id from get_answering_line; a line that is still being set up returns an error. Returns { alias, sip_uri, sip_uri_tls, username, password }; keep the username and password private. The address is created once and repeat calls return the same one. SIP calls use the line's normal balance with no separate SIP charge. Needs lines:manage; rate limited per account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "line_id": "<line_id>"
    },
    "name": "create_sip_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_idYesFrom get_answering_line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the idempotent create-once behavior (corroborating idempotentHint), the setup-in-progress error path, the required lines:manage permission, per-account rate limiting, and the billing model (normal line balance, no separate SIP charge). It also warns that username and password are secrets, which is critical handling context for an openWorld 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?

Purpose and the alternate tool come first, followed by prerequisites, return shape, cost, and permissions in a compact paragraph. Every clause carries actionable information; nothing is filler.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description enumerates the return fields, states the idempotency contract, the error case, the permission scope, and the rate limit. An agent has everything needed to call it and interpret the result.

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?

Schema coverage is 100% and the schema already says 'From get_answering_line', so the baseline is satisfied. The description adds meaning beyond the schema by explaining that an in-setup line causes an error and by tying the parameter to the correct upstream tool.

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 states a concrete verb pair and resource: create-on-first-call or read the SIP address and private trunk credentials for one of the owner's answering lines. It also states the purpose (let the phone system send calls over SIP without a phone number) and distinguishes itself from get_answering_line, which handles the number and forwarding codes.

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

Usage Guidelines5/5

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

Explicit routing is provided: use get_answering_line for the line's number and forwarding codes, and this tool for the SIP address. Prerequisites (pass line_id from get_answering_line) and the failure condition (a line still being set up returns an error) are both stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.