Skip to main content
Glama
kostikpenzin

mcp-iva-mcu

by kostikpenzin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

iva_conference_session_groups

Manage conference breakout rooms by creating, activating, deactivating, or removing session groups; extend duration, move participants, and fetch groups.

Instructions

IVA conference session groups: create/activate/deactivate/remove groups, extend duration, move participants, get groups. Clients API v2.28.12.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform: - "activate": Активировать группы сессии. / Activate session groups. - "create": Создать группы в сессии (например, сессионные залы). / Create session groups (e.g., breakout rooms). - "deactivate": Деактивировать группы сессии. / Deactivate session groups. - "extend_duration": Продлить длительность группы сессии. / Extend session group duration. - "get": Получить группы сессии. / Get session groups. - "move_participants": Переместить участников между группами. / Move participants between groups. - "remove": Удалить группы сессии. / Remove session groups.
confirmNoSet to true to confirm destructive actions (delete, remove, stop, etc.) when IVA_CONFIRM_DESTRUCTIVE is enabled.
moveDataNoMove participants data
extendDataNoExtend duration data
groupsDataNoGroup creation data
removeDataNoRemove groups data (groupIds)
activateDataNoGroup activation data (groupIds)
deactivateDataNoGroup deactivation data (groupIds)
conferenceSessionIdNoConference session UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.8

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It names mutating operations such as remove and deactivate, but does not explain destructive consequences, required permissions, confirmation behavior, or session-wide effects. The confirm parameter exists in the schema, yet the description never mentions when confirmation is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence that front-loads the resource name and lists the main operations. It is appropriately sized, though the version suffix 'Clients API v2.28.12' adds limited value and the dense listing could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity tool with nine parameters, seven actions, nested objects, and no output schema, yet the description provides only a one-line overview. It misses operation-specific expectations, return behavior, and practical effects of destructive actions, making it incomplete for safe invocation.

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%, and the action enum values already describe each operation in detail. The tool description repeats operation names but adds no parameter-level meaning beyond the schema, so it meets the baseline without compensating further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource (IVA conference session groups) and enumerates the supported operations: create, activate, deactivate, remove, extend duration, move participants, and get. It clearly states what the tool does, though it does not explicitly differentiate it from related sibling tools such as iva_conference_participants or iva_conference_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus the many conference-related sibling tools, nor does it describe prerequisites or contexts for each action. The operation list implies group-management usage, but the agent is left to infer appropriate scenarios.

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