Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a SIP credential

trunk_delete_credential
Destructive

Deletes a SIP credential from a trunk group and clears it from Redis and Kamailio usrloc. Idempotent, returns 204 if already absent. Find the credential ID with trunk_list_credentials.

Instructions

Delete a SIP credential and cascade removal from Redis + Kamailio usrloc. Idempotent (returns 204 when already gone). Use trunk_list_credentials first to find the credential id. Step-up MFA required. Errors: INVALID_ID, NO_ACTIVE_CUSTOMER, TRUNK_UNOWNED, NOT_FOUND, INTERNAL_ERROR.

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": {
      "trunk_id": "<trunk_id>",
      "cred_id": "<cred_id>"
    },
    "name": "trunk_delete_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
cred_idYesSIP credential UUID (find it with trunk_list_credentials)
trunk_idYesTrunk group UUID (find it with trunk_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior3/5

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

Discloses cascade removal, idempotency, MFA, and errors, but contradicts the annotation idempotentHint=false by stating the operation is idempotent. This inconsistency undermines transparency.

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

Conciseness5/5

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

Two efficient sentences plus error list. Front-loaded with action and key details. No wasted words.

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

Completeness3/5

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

Covers prerequisites, idempotency, MFA, and errors, but the idempotency contradiction with annotations leaves uncertainty. Lacks mention of output format or HTTP status codes beyond 204.

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% with adequate descriptions. The description adds no extra meaning beyond referencing trunk_list_credentials for cred_id. Baseline score due to high coverage.

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?

Clearly states the verb 'Delete' and resource 'SIP credential', with additional context of cascade removal from Redis and Kamailio usrloc. Distinguishes from sibling tools like trunk_create_credential and trunk_list_credentials.

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?

Explicitly instructs to use trunk_list_credentials first, notes idempotency and Step-up MFA requirement, and lists expected errors. Provides clear when-to-use and what-to-expect.

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

Deploy Server

Other Tools