Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List live conferences

list_conferences
Read-only

Retrieve names of active conference rooms on your Vobiz account to find a room for get_conference or member tools; ended rooms are excluded and an empty result is normal.

Instructions

List the names of the conference rooms running right now on this Vobiz account (GET /Conference/). Rooms that have ended are not listed, there is no paging, and an empty list is a normal result. Use it to find a room name for get_conference or the member tools; for the history of a finished room use list_call_records.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
noteNoPresent when no room is running.
countNoNumber of live rooms.
conferencesNoNames of the rooms running now, exactly as used in <Conference>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "conferences": {
+      "description": "Names of the rooms running now, exactly as used in <Conference>.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of live rooms.",
+      "type": "number"
+    },
+    "note": {
+      "description": "Present when no room is running.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "True on success; false when the result is an error (then error, message and retryable are set).",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: ended rooms are excluded, there is no paging, and an empty list is a normal (non-error) result. Only minor gap is whether the list can be large enough to matter, but that is largely addressed by the no-paging note.

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 sentences, front-loaded with the scope, then edge-case behavior, then sibling routing. Every sentence carries information an agent needs; nothing is redundant with the title or schema.

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?

With an output schema present, return-shape detail is unnecessary, and annotations cover the safety profile. The description still covers scope, exclusions, paging behavior, empty-result semantics, and downstream tool routing, so 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.

Parameters4/5

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

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly avoids inventing filter syntax and instead frames the call as unfiltered.

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 ('List the names of the conference rooms') plus the exact scope ('running right now on this Vobiz account') and even the underlying endpoint. An agent can distinguish it from get_conference and the member tools without opening a 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 routes the agent: use this to obtain a room name for get_conference or the member tools, and use list_call_records instead for history of a finished room. Both the when-to-use and the named alternative are stated, not implied.

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