Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Hang up a call

end_call
DestructiveIdempotent

Terminate an active or queued call for all parties after explicit user confirmation. Requires call_uuid and confirm: true.

Instructions

Terminate an active or queued call (DELETE /Account/{auth_id}/Call/{call_uuid}/) for every party on it. Checks first that the call is live or queued on this account. To move the call elsewhere instead use transfer_call; to park a leg use hold_call. Required: call_uuid and confirm: true after the user explicitly asked to end this call. Fails with call_not_active if the call already ended and not_found if no such call exists on the account.

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true, set only after the user explicitly asked to end this call.
call_uuidYesUUID of the call to end: the request_uuid from make_call, or a UUID from list_live_calls.

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`.
noteNoWhere the final record will appear (get_call_details).
call_uuidNoThe call UUID the request was about, echoed back.
terminatedNoTrue once Vobiz accepted the hangup.
http_statusNoHTTP status Vobiz answered with.
previous_stateNoWhether the call was in progress or still waiting to be dialed when it was ended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / properties / call_uuid / description
      Previous value: -"UUID of the call to end."New value: +"UUID of the call to end: the request_uuid from make_call, or a UUID from list_live_calls."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "call_uuid": {
+      "description": "The call UUID the request was about, echoed back.",
+      "type": "string"
+    },
+    "http_status": {
+      "description": "HTTP status Vobiz answered with.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "note": {
+      "description": "Where the final record will appear (get_call_details).",
+      "type": "string"
+    },
+    "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"
+    },
+    "previous_state": {
+      "description": "Whether the call was in progress or still waiting to be dialed when it was ended.",
+      "enum": [
+        "live",
+        "queued"
+      ],
+      "type": "string"
+    },
+    "terminated": {
+      "const": true,
+      "description": "True once Vobiz accepted the hangup.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (destructive, non-readOnly, openWorld), and the description adds genuinely new context: the blast radius (terminates for every party), the live/queued precheck, and the two distinct failure modes (call_not_active, not_found). This goes well beyond what the annotations 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?

Four tight sentences, front-loaded with the action and scope, then alternatives, then preconditions, then error behavior. No filler and every clause carries information an agent needs.

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?

For a destructive two-parameter tool with full schema coverage, an output schema, and full annotations, this description supplies the remaining gaps: scope of termination, preconditions, and error semantics. Nothing needed to call it correctly is missing.

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 both parameters are already documented in the schema, including the confirm semantics. The description restates the confirm requirement without adding syntax or format detail beyond the schema — the baseline 3 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?

States a specific verb and resource (terminate a call), the exact scope (active or queued, for every party on it), and even the underlying endpoint. It distinguishes itself from transfer_call and hold_call, which are named directly.

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?

Explicit alternatives are named with their selecting conditions (move the call → transfer_call; park a leg → hold_call), and the precondition for invocation is spelled out (confirm: true only after the user explicitly asked to end this call).

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