Skip to main content
Glama
Sign In
Vobiz MCP Server

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

End a live conference

end_conference
DestructiveIdempotent

Hang up a running Vobiz conference room so every member is disconnected at once and the room closes. Use it to end a meeting on time or clear an abandoned room; requires confirm: true.

Instructions

Hang up one running Vobiz conference room (DELETE /Conference/{name}/): every member is disconnected at once and the room ends. Use it to close a meeting on time or clean up an abandoned room; to remove only some people, use kick_conference_member or hangup_conference_member. Requires confirm: true. A room that is not running returns the not_found 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": {
      "conference_name": "<conference_name>",
      "confirm": "<confirm>"
    },
    "name": "end_conference"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true, set only after the user explicitly asked to end this conference for everyone in it.
conference_nameYesConference room name, exactly as used in the <Conference> XML element.

Output Schema

NameRequiredDescriptionDefault
okNoTrue on success; false when the result is an error (then error, message and retryable are set).
endedNoAlways true: the room is gone.
http_statusNoHTTP status Vobiz answered with (202 = accepted, 204 = done).
conference_nameNoRoom the action was applied to.

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": {
+    "conference_name": {
+      "description": "Room the action was applied to.",
+      "type": "string"
+    },
+    "ended": {
+      "const": true,
+      "description": "Always true: the room is gone.",
+      "type": "boolean"
+    },
+    "http_status": {
+      "description": "HTTP status Vobiz answered with (202 = accepted, 204 = done).",
+      "type": "number"
+    },
+    "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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is partly carried. The description adds real context beyond them: the blast radius (all members disconnected, room ends), the confirm gate, and the not_found error for a non-running room. It stops short of describing the response payload, but the output schema covers that.

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 tight sentences, front-loaded with the destructive scope, then the alternatives, then the prerequisite and error case. Every sentence earns its place and none is redundant filler.

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, single-target tool with an output schema, the description covers scope, alternatives, the confirm prerequisite, and the not_found failure mode. An agent has everything needed to invoke it correctly; return values are handled by the output schema.

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 (confirm, conference_name) are fully documented in the schema; baseline 3 applies. The description restates 'Requires confirm: true' but adds no naming syntax or format detail beyond the schema's pattern and description.

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 ('Hang up one running Vobiz conference room ... DELETE /Conference/{name}/') and immediately distinguishes scope: the whole room ends and every member is disconnected at once. An agent can tell this apart from kick_conference_member/hangup_conference_member without opening either 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 when to use it ('close a meeting on time or clean up an abandoned room') and routes to the alternatives for the partial case ('to remove only some people, use kick_conference_member or hangup_conference_member'). Nothing is left to inference.

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