Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a trunk endpoint

trunk_delete_endpoint
Destructive

Remove a dispatcher endpoint from a SIP trunk and drop it from Kamailio. Find the endpoint ID first with trunk_list_endpoints.

Instructions

Remove a dispatcher endpoint from an owned trunk and drop it from Kamailio. Use trunk_list_endpoints first to find the endpoint id. Step-up MFA required. Errors: NO_ACTIVE_CUSTOMER, INVALID_ID, 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>",
      "endpoint_id": "<endpoint_id>"
    },
    "name": "trunk_delete_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
trunk_idYesTrunk group UUID (find it with trunk_list)
endpoint_idYesEndpoint ID (integer, find it with trunk_list_endpoints)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description adds that it 'drops from Kamailio' and lists specific error codes (NO_ACTIVE_CUSTOMER, INVALID_ID, NOT_FOUND, INTERNAL_ERROR), providing additional context beyond the structured annotations.

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 sentences plus an error list. Front-loaded with the primary action, no unnecessary words, every sentence contributes value.

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?

The description covers the action, prerequisites, and possible errors. However, it lacks explanation of the expected successful response or side effects beyond deletion. For a destructive operation with no output schema, this is a notable gap.

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 description coverage is 100%, so the schema already documents both parameters. The description only reinforces 'find it with trunk_list_endpoints' but adds no new parameter semantics beyond the schema.

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?

The description clearly states 'Remove a dispatcher endpoint from an owned trunk and drop it from Kamailio', specifying the verb, resource, and scope. It distinguishes from siblings like trunk_delete (removes entire trunk) and trunk_delete_credential.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides actionable guidance: 'Use trunk_list_endpoints first to find the endpoint id' and mentions 'Step-up MFA required'. While it doesn't explicitly state when not to use, the prerequisite and security note offer clear usage context.

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