Skysay

Resume sip connection

resume_sip_connection

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>"
    },
    "name": "resume_sip_connection"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	No
`connection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the lower bar applies, yet the description still adds nothing specific about the effect of resuming, which state it transitions from or to, its permissions, or whether it is repeatable. It does mention write-only passwords and rate limits, but those are behaviors of neighbouring operations, and 'No carrier settings change' sits awkwardly beside a state-changing resume.

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

Conciseness2/5

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

It opens with marketing framing ('Bring your own SIP trunk') rather than the action, then sprawls through the behaviour of at least four sibling tools in long run-on sentences. Much of the text does not earn its place for this tool.

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

Completeness2/5

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

For a state-changing tool with no output schema, two parameters and zero schema descriptions, the description should cover the resume action, its preconditions and its parameters. Instead it covers unrelated operations, so an agent knows less about this tool after reading it than the name alone would suggest.

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?

Schema description coverage is 0% for two parameters, so the description must explain them and does not. Neither connection_id nor project_id is mentioned, and it does not say what happens if the connection is already active or in another state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and title say 'resume a SIP connection', but the description never uses the word resume or explains what resuming does. Instead it describes the whole SIP-trunk family ('create, read or change a carrier SIP connection'), so an agent cannot tell what this specific tool actually performs.

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?

There is no when-to-use guidance for resuming versus the sibling tools disable_sip_connection, update_sip_connection or get_sip_connection. The side-effect notes (verification calls, billed test calls, rate limits) belong to other tools such as attach_sip_connection_number and start_sip_connection_test_call, so they do not help select this one.

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

All Skysay tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?