Skip to main content
Glama
vobiz-ai

Vobiz MCP Server

Official
by vobiz-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

End a live conference

end_conference
DestructiveIdempotent

Closes a running Vobiz conference room and disconnects every member at once; use it to end meetings on time or clean up abandoned rooms, with explicit confirmation required.

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.

Input Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, and readOnlyHint=false, so the safety profile is covered. The description adds value by clarifying that the blast radius is the entire room and that confirm:true is mandatory, which is behavior beyond the raw flags.

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?

Front-loads the action and its scope, then the usage case, then the alternative, then the prerequisite. Every clause earns its place and nothing is redundant padding.

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 two-parameter destructive tool with full schema coverage and annotations covering the safety profile, the description supplies everything needed: scope, effect, alternatives, and the confirm gate. No output schema is needed or expected.

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 gating semantics. The description only restates the confirm requirement, adding no syntax or naming detail beyond the schema. 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 ('Hang up one running Vobiz conference room'), gives the HTTP endpoint, and describes the exact effect (all members disconnected, room ends). An agent can distinguish it from sibling conference 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?

Names two concrete scenarios (close a meeting on time, clean up an abandoned room) and explicitly routes partial removal to kick_conference_member or hangup_conference_member. The when/when-not split is complete.

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