Skip to main content
Glama
Sign In

Skysay

by io.github.skysay-ai
OverviewDiscussionsAdmin

Check sip connection reachability

check_sip_connection_reachability

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": "check_sip_connection_reachability"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful specifics: it performs one SIP OPTIONS request and does not change carrier settings. It still omits permissions, rate limits for this specific tool, and what happens on failure.

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 definition is a long, mixed-purpose paragraph covering create/read/change operations, password handling, number attachment, ownership checks, and test calls. The information relevant to this specific tool appears only in the final sentences and is not front-loaded.

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 two-parameter tool with no output schema, the definition should at least explain connection_id and success/failure behavior. Instead it spends most of its space on sibling tools and leaves the caller without enough context to invoke this tool confidently.

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 the two parameters, so the description must compensate. It never mentions connection_id or project_id and gives no guidance on what connection_id identifies or how project scoping works.

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

Purpose3/5

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

The description eventually states that check_sip_connection_reachability sends one SIP OPTIONS to the carrier server, which is specific. However, it opens with unrelated SIP connection CRUD operations and buries the actual purpose at the end, so an agent scanning the definition could be misled about what this tool does.

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 contrasts this tool with start_sip_connection_test_call by noting that the latter places a billed call while reachability sends a SIP OPTIONS probe. That implicitly helps with tool selection, but there is no explicit when-to-use or when-not-to-use guidance for reachability itself, nor any note about ownership prerequisites.

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