Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete trunk origination URI

delete_origination_uri
DestructiveIdempotent

Remove an outbound origination URI from the Vobiz account by UUID; this irreversible action stops trunks routing calls to that destination.

Instructions

Delete an origination URI from this Vobiz account; this cannot be undone. Trunks stop routing outbound calls to that destination, so add a replacement with create_origination_uri and re-point the trunk with update_sip_trunk first if it is a trunk's only route. An unknown uri_id raises not_found. Gated by VOBIZ_ENABLE_PROVISIONING and confirm: true.

Input Schema

NameRequiredDescriptionDefault
uri_idYesOrigination URI UUID: the id from list_origination_uris or create_origination_uri. Unknown ids raise not_found.
confirmYesMust be true, set only after the user explicitly approved: deleting this origination URI.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success. On a failure the result is isError with ok: false plus `error` (kind), `message`, `retryable` and sometimes `http_status`.
uri_idNoThe URI that was deleted.
deletedNo
http_statusNoHTTP status Vobiz answered with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • addedInput schema / properties / uri_id / description
      Added value: +"Origination URI UUID: the id from list_origination_uris or create_origination_uri. Unknown ids raise not_found."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "deleted": {
+      "const": true,
+      "type": "boolean"
+    },
+    "http_status": {
+      "description": "HTTP status Vobiz answered with.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "True on success. On a failure the result is isError with ok: false plus `error` (kind), `message`, `retryable` and sometimes `http_status`.",
+      "type": "boolean"
+    },
+    "uri_id": {
+      "description": "The URI that was deleted.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this destructive and non-readOnly, but the description adds real substance beyond them: the deletion is irreversible, the operational consequence is that trunks stop routing outbound calls to that destination, and an unknown uri_id raises not_found. That is exactly the kind of blast-radius and error context annotations cannot convey.

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?

Irreversibility is front-loaded in the first clause, then consequences, then the remediation path, then gates. No sentence is filler and the ordering follows the order an agent needs the information.

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?

A destructive, gated mutation with an output schema; the description covers risk, consequence, preconditions, error behavior and required confirmation. Nothing material is left for the agent to infer before calling.

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

Parameters5/5

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

Schema coverage is 100%, so both parameters are already documented, but the description reinforces the gating semantics ('Gated by ... confirm: true') and the not_found behavior for uri_id, tying the parameters to the failure and safety model rather than just restating types.

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?

States a specific verb (Delete) and resource (origination URI) scoped to 'this Vobiz account', and immediately flags irreversibility. It is trivially distinguishable from the sibling create_origination_uri, update_origination_uri and list_origination_uris.

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?

Gives an explicit precondition ('if it is a trunk's only route') and names the alternative tools to run first (create_origination_uri, update_sip_trunk). It also states the enablement gates (VOBIZ_ENABLE_PROVISIONING, confirm: true), so the agent knows when the call will even succeed.

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