Caly

Disconnect video app

disconnect_conferencing

Destructive

Disconnect a video-conferencing app from the account. Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user what will happen, then call again with the SAME arguments plus confirmToken.

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": {
      "app": "<app>"
    },
    "name": "disconnect_conferencing"
  }
}

Input Schema

Name	Required	Description	Default
`app`	Yes	Video app id from list_conferencing_apps, e.g. zoom, google-meet, office365-video, daily-video.
`confirmToken`	No	Leave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real context beyond the annotations: the destructive action is gated by a two-step handshake returning CONFIRMATION_REQUIRED plus a confirmToken, and the agent is told to inform the user before proceeding. That is exactly the kind of protocol disclosure annotations (destructiveHint, idempotentHint) cannot convey. It omits one meaningful consequence - whether event types or bookings currently using that app are affected.

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?

Two sentences, no filler. The action is front-loaded and the multi-step protocol follows immediately, matching the order in which the agent needs the information.

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

Completeness4/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 no output schema, the definition covers the hard part (the confirmation round-trip and the token). Completeness is slightly reduced by not stating what a successful final response looks like or what happens downstream to conferencing-dependent event types.

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?

Schema coverage is 100%, so both parameters are already documented, and the description does not re-explain them needlessly. It does add one genuinely useful constraint the schema does not state: the second call must repeat the SAME arguments plus the token, which changes how the agent must retain and reuse input.

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?

Specific verb ('Disconnect') plus a precise resource ('a video-conferencing app from the account'), which separates it from connect_conferencing and from the generic disconnect. It stops short of naming the near-neighbour siblings (disconnect_calendar, disconnect_google_workspace) that an agent might confuse it with, so it is clear but not sibling-differentiated by name.

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

Usage Guidelines3/5

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

The correct invocation sequence is spelled out, but there is no explicit statement of when to choose this over the plain 'disconnect' or 'disconnect_calendar' tools, and no prerequisites (e.g. ownership/admin rights) or exclusions. Usage is implied by the resource name rather than guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Caly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?