Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a trunk IP ACL entry

trunk_delete_ip_acl
Destructive

Remove an IP ACL entry from a trunk to stop that source IP from sending calls via IP auth. Find the IP ID using trunk_list_ips before deletion.

Instructions

Remove an IP ACL entry from an owned trunk; that source IP can no longer send calls via IP auth. Use trunk_list_ips first to find the ip_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>",
      "ip_id": "<ip_id>"
    },
    "name": "trunk_delete_ip_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
ip_idYesIP ACL entry UUID (find it with trunk_list_ips)
trunk_idYesTrunk group UUID (find it with trunk_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false. Description adds the 'Step-up MFA required' context and the consequence of the IP being blocked. No contradictions.

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?

Three sentences with no superfluous words. Purpose, prerequisite, and error codes are presented efficiently.

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

Completeness5/5

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

Tool is simple (delete an ACL entry). Description covers purpose, prerequisite, consequence, MFA requirement, and error codes. No output schema needed.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. Description adds value by referencing trunk_list_ips and trunk_list, providing guidance 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?

Description clearly states 'Remove an IP ACL entry from an owned trunk' with the consequence 'source IP can no longer send calls via IP auth'. This distinguishes it from sibling tools like trunk_add_ip_acl and trunk_update_ip_acl.

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 a clear prerequisite ('Use trunk_list_ips first to find the ip_id') and mentions 'Step-up MFA required'. Does not explicitly state when not to use or list alternatives, but context is adequate.

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