Skip to main content
Glama
Sign In

Skysay

by io.github.skysay-ai
OverviewDiscussionsAdmin

Save sip connection dial format

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

Input Schema

NameRequiredDescriptionDefault
number_idYes
project_idNo
test_call_idYesAn answered test call of this number.
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=false, so the agent knows a clobbering write happens, yet the description never says what is overwritten or whether the prior dial format is recoverable. The added context (write-only passwords, verification-call rate limits, outbound refusal until ownership is confirmed) is genuine but belongs to the SIP family and other tools, not to this operation.

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?

The text is a single run-on block that spends most of its length on sibling tools and service-wide policies. The actual operation is never front-loaded, so the reader must scan past unrelated facts to find nothing about 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 destructive, non-idempotent mutation with four parameters and no output schema, the description should explain the prerequisite relationship between test_call_id and connection_id/number_id, what a dial format is, and what changes on success. None of that is present; the annotations do the heavy lifting while the text covers other tools.

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

Parameters1/5

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

Schema description coverage is only 25% — only test_call_id is documented. The description explains none of number_id, connection_id, or project_id, and does not compensate for the gap. Nothing tells the agent why a test_call_id of an *answered* call is required, which is the one non-obvious parameter.

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 description describes the SIP trunk family ("create, read or change a carrier SIP connection and its numbers") but never states what saving a *dial format* means or does. Nothing in the text mentions a dial format, so an agent cannot tell what this tool actually writes, nor how it differs from create_sip_connection or update_sip_connection.

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?

It gives usage context for sibling tools (ownership check, test call, reachability check) including rate limits and billing, but never says when to call save_sip_connection_dial_format instead of update_sip_connection or attach_sip_connection_number. The one hint is the required test_call_id, whose meaning is only implied by the schema.

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

All Skysay toolsInspect
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