Skip to main content
Glama
Sign In
warp-mcp

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a trunk

trunk_update
Idempotent

Update a SIP trunk's settings for name, authentication, capacities, and SIP configuration. Find the trunk ID via trunk_list, then apply changes with step-up MFA enforced.

Instructions

Update an owned trunk's settings (name, auth type, capacities, SIP config). The trunk being updated is excluded from the account capacity-sum check. POI assignment is silently ignored (admin-only). Step-up MFA required. Use trunk_list first to find the trunk id. Errors: NO_ACTIVE_CUSTOMER, INVALID_ID, NOT_FOUND, INVALID_PAYLOAD, VALIDATION_ERROR, 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>"
    },
    "name": "trunk_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTrunk name
trunk_idYesTrunk group UUID (find it with trunk_list)
auth_typeNoAuthentication mode: IP_ACL, DIGEST, EITHER, or BOTH
sip_configNoSIP config object persisted as JSONB (e.g. { codecs: [...], dtmf_mode: '...' }). The customer portal only writes codecs and dtmf_mode; other keys are admin-surface.
descriptionNoFree-text description of the trunk
capacity_cps_inboundNoMax inbound calls-per-second; 0 disables inbound (503 + Retry-After at runtime)
capacity_cps_outboundNoMax outbound calls-per-second; 0 disables outbound
allowed_number_classesNoNumber classes this trunk may carry
capacity_channels_inboundNoMax concurrent inbound channels; 0 disables inbound
capacity_channels_outboundNoMax concurrent outbound channels; 0 disables outbound

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior5/5

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

Adds significant behavioral context beyond annotations: the trunk is excluded from capacity-sum check, POI assignment is silently ignored, and Step-up MFA is required. No contradiction with annotations (idempotentHint=true is consistent with update semantics).

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 description is succinct, front-loads the main purpose, and adds relevant details without extraneous text. Slightly verbose with error list but still efficient.

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?

Covers errors, prerequisites, and behavioral quirks. Lacks description of return value or side effects, but given no output schema, this is acceptable. Could be more complete for a complex tool.

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 descriptions cover all 10 parameters comprehensively (100% coverage). The tool description adds minimal additional meaning beyond echoing schema fields, so baseline score 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?

The description clearly states 'Update an owned trunk's settings' with specific fields listed (name, auth type, capacities, SIP config). It distinguishes from sibling operations like trunk_create and trunk_delete.

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 explicit prerequisite ('Use trunk_list first to find the trunk id') and mentions special conditions (POI silently ignored, Step-up MFA required). Does not explicitly state when not to use or list alternatives, but context is 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