Skip to main content
Glama
Sign In
mcp-iva-mcu

mcp-iva-mcu

by kostikpenzin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

iva_devices

Register or deregister user devices (phone, softphone) for SIP/VoIP. Provide deviceId, profileId, and deviceData to manage user device registration.

Instructions

IVA device management: register and deregister user devices. Clients API v2.28.12.

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": {
      "action": "<action>"
    },
    "name": "iva_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesOperation to perform: - "register": Register a user device (phone, softphone, etc.) for SIP/VoIP. Зарегистрировать устройство пользователя. - "deregister": Deregister/unregister a user device. Снять регистрацию устройства. Удалить устройство.
confirmNoSet to true to confirm destructive actions (delete, remove, stop, etc.) when IVA_CONFIRM_DESTRUCTIVE is enabled.
deviceIdNoDevice UUID
profileIdNoProfile (user) UUID
deviceDataNoDevice registration data

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?

No annotations are present, so the description carries the full burden of behavioral disclosure. It identifies register/deregister as the operations but does not state that deregistration is destructive, whether confirmation may be required, or what side effects or prerequisites exist. The confirm parameter is only documented in the schema, not in the description.

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 main sentence is short and front-loaded with the key purpose. The trailing 'Clients API v2.28.12' is minor extra context, not harmful, but it does not earn its place as strongly as the core sentence.

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?

For a tool with five parameters, nested deviceData, and no output schema, the description provides only a high-level summary. It does not clarify which parameters apply to register versus deregister, what deviceData should contain, or which operations need confirmation, so an agent could still struggle to invoke it correctly.

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 the structured schema already documents action, confirm, deviceId, profileId, and deviceData. The description adds no extra meaning beyond the schema, which places it at the baseline of 3 rather than higher.

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 states a clear resource ('user devices') and specific operations ('register and deregister'), so an agent can identify the tool's core function. It does not explicitly contrast it with sibling tools, but none of the listed siblings obviously overlaps with device registration management.

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?

The description gives no guidance on when to choose this tool over alternatives, nor does it mention prerequisites or conditions for registration versus deregistration. The action enum hints at the two flows, but the description itself provides no decision context.

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