Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a trunk IP ACL entry

trunk_update_ip_acl
Idempotent

Update an IP ACL entry on a SIP trunk by changing its description or enabled state. Find the ip_id with trunk_list_ips before calling this tool.

Instructions

Update the description and/or enabled flag of an owned trunk's IP ACL entry. Use trunk_list_ips first to find the ip_id. Step-up MFA required. Errors: NO_ACTIVE_CUSTOMER, INVALID_ID, NOT_FOUND, INVALID_PAYLOAD, 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_update_ip_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
ip_idYesIP ACL entry UUID (find it with trunk_list_ips)
enabledNotrue to enable the ACL entry, false to disable it
trunk_idYesTrunk group UUID (find it with trunk_list)
descriptionNoNew free-text label for the ACL entry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the MFA requirement and a list of error codes, giving valuable context beyond structured fields.

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 concise sentences: purpose, prerequisite step, and error list. Every sentence earns its place with no wasted words.

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?

Given no output schema and a simple update operation, the description covers prerequisites, MFA, and errors. It could mention success behavior, but the idempotent hint reduces the need. Still, slightly incomplete.

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 descriptions for all 4 parameters. The description only reinforces the schema's guidance for ip_id (find with trunk_list_ips), adding no new semantic meaning beyond what's already documented.

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 the verb 'update' and the specific resource 'IP ACL entry of an owned trunk', distinguishing it from sibling tools like trunk_add_ip_acl and trunk_delete_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?

It provides explicit guidance: 'Use trunk_list_ips first to find the ip_id', lists possible errors, and mentions MFA requirement. It does not explicitly exclude alternatives but is still clear.

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