Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

list_sip_credentials

Read-only

List a number's SIP credentials (passwords masked), plus active_count and limit so you can tell how many more the number may hold. A credential carrying an extension is a PERSON'S LINE: their desk phone registers with its SIP password, and their app devices (laptop, mobile) attach to the same line by connection code, so dialling the extension rings all of them. A credential without an extension is just one device registration.

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

Input Schema

NameRequiredDescriptionDefault
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
number_idYestenant number UUID (from list_numbers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), but the description adds substantive context beyond them: passwords are masked, active_count and limit are returned so capacity can be computed, and it explains the extension/no-extension distinction and how desk phones and app devices share a line. That is genuine domain reasoning an agent would otherwise have to guess.

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 core operation and return fields are front-loaded in the first sentence, with the extension explanation following as supporting context. It is longer than strictly necessary, but the second and third sentences carry information an agent needs to interpret credential rows correctly rather than restating the name.

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

Completeness4/5

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

For a two-parameter read tool with no output schema, the description explains what is returned (masked credentials, active_count, limit) and how to interpret the credential records. Minor gaps remain, such as ordering or masking format, but nothing essential to correct invocation is missing.

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

Parameters3/5

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

Schema coverage is 100%, so both number_id and purpose are already fully documented in the schema, including the pointer to list_numbers and the report-tool caveat. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ('List a number's SIP credentials') and adds scope detail that separates it from sibling tools like create_sip_credential, reveal_sip_credential and rotate_sip_credential. An agent can distinguish this read-only listing from the mutation and secret-reveal siblings without opening any schema.

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 implies purpose ('so you can tell how many more the number may hold'), which gives an implicit when-to-use signal, but never states explicit conditions or points to alternatives such as reveal_sip_credential for the plaintext password or get_number for number metadata. Usage is inferable rather than stated.

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

All Sautikit 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