Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List live calls

list_live_calls
Read-only

Get the UUIDs of every call in progress on your account, and queued calls if include_queued is true. Pass a UUID to check status or use in-call controls.

Instructions

List the UUIDs of every call currently in progress on this account (GET /Call/?status=live), plus the queued ones (accepted, not yet dialed) when include_queued is true. Returns UUIDs only, read from Vobiz at the moment of the request: pass one to get_call_status for its state, or to the in-call tools (speak_text, play_audio, transfer_call, end_call). Finished calls are not listed; use list_call_records for those. An empty list means no call is live right now, not an error.

Input Schema

NameRequiredDescriptionDefault
include_queuedNoAlso return queued_calls (accepted by Vobiz, not yet dialed). Default false: only live calls are fetched.

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`.
live_callsNoUUIDs of calls ringing or in progress right now.
live_countNoNumber of entries in live_calls.
queued_callsNoOnly with include_queued: UUIDs of calls accepted but not yet dialed.
queued_countNoOnly with include_queued: number of entries in queued_calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / properties / include_queued / description
      Previous value: -"Also list queued (accepted, not yet dialed) calls. Default false."New value: +"Also return queued_calls (accepted by Vobiz, not yet dialed). Default false: only live calls are fetched."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "live_calls": {
+      "description": "UUIDs of calls ringing or in progress right now.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "live_count": {
+      "description": "Number of entries in live_calls.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "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"
+    },
+    "queued_calls": {
+      "description": "Only with include_queued: UUIDs of calls accepted but not yet dialed.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "queued_count": {
+      "description": "Only with include_queued: number of entries in queued_calls.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior not in the annotations: results are read live at request time, only UUIDs are returned, and an empty list means no live calls rather than an error. That empty-result semantics is the kind of detail that prevents agent misreads.

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 sentences, front-loaded with the core scope, followed by the endpoint, the queued qualifier, the follow-up routing, and the empty-result clarification. No sentence is wasted; each adds a distinct piece of 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?

For a one-parameter read-only list tool with an output schema covering return shape, this description covers scope, follow-up usage, and empty-result behavior. Nothing needed to invoke 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 coverage is 100% and the single parameter is documented in the schema, including the same 'accepted, not yet dialed' wording used in the description. The description largely restates the schema's meaning for include_queued, so baseline 3 is appropriate.

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 (List), resource (UUIDs of calls in progress), and scope (this account, live only), and explicitly routes to the sibling for the other case (list_call_records for finished calls). An agent can distinguish it from list_call_records and get_call_status without opening any schema.

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?

Explicitly names the follow-up path (pass a UUID to get_call_status or the in-call tools) and the exclusion condition (finished calls are not listed; use list_call_records). When-to-use and when-not-to-use are both stated with the alternative named.

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