Skip to main content
Glama

Check sip connection number ownership

check_sip_connection_number_ownership
Destructive

Bring your own SIP trunk: create, read or change a carrier SIP connection and its numbers through the same service as /v1/sip-connections. Passwords are write-only and never returned. Attaching a number for incoming calls, and check_sip_connection_number_ownership, place one Skysay verification call to that number (rate limited per number and per workspace); outbound with the number is refused until its ownership is confirmed. start_sip_connection_test_call places one billed call (calls:write) from the number to the given phone; check_sip_connection_reachability sends one SIP OPTIONS to the carrier server. No carrier settings change.

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": {
      "connection_id": "<connection_id>",
      "number_id": "<number_id>"
    },
    "name": "check_sip_connection_number_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
number_idYes
project_idNo
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

While annotations already flag the tool as destructive (destructiveHint: true), the description adds key behavioral traits not captured structurally. It specifies that the tool uses a verification call, is rate limited per number/workspace, and has no effect on carrier settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but highly effective, packing numerous critical constraints (billing, rate limits, required workflow steps) into a few sentences without unnecessary filler. Although long, every element provides necessary value.

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?

Given the complexity of this specialized SIP workflow, the definition is remarkably complete. It covers the operational triggers, the prerequisites for using the number (ownership confirmation), and the limitations (rate limits).

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

Parameters2/5

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

The schema coverage is 0%, meaning the description bears a massive burden. While the context is clear (it operates on 'connection_id' and 'number_id' in the context of a SIP trunk), the description offers no deep semantic meaning or explanation of these parameters beyond their immediate operational usage.

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 defines the function as checking SIP connection number ownership. It distinguishes this from related tools by stating it uses a verification call, unlike check_sip_connection_reachability which only sends a SIP OPTIONS request.

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?

The definition provides extensive operational guidance, specifying that this tool is required for inbound numbers to be used, and critically, that outbound calls are refused until ownership is confirmed. It also distinguishes its purpose from billing calls (start_sip_connection_test_call).

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.

Resources