Onda MCP

Overview Schema Source Related Servers Discussions Admin

onda_terminal_unsubscribe

Detach a terminal listener session to free the ring buffer. Call when done to release memory and reset to idle size.

Instructions

Detach a listener session. Idempotent. Always call this when done to free the ring buffer (drops back to idle size after the last subscriber leaves).

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": {
      "sessionId": "<sessionId>"
    },
    "name": "onda_terminal_unsubscribe"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Session ID to detach.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Aug 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals idempotency and the side effect of freeing the ring buffer, including the 'drops back to idle size after the last subscriber leaves' detail. It does not mention error handling or return values, but for a simple detach tool this is sufficient.

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?

The description is two sentences long with zero filler. The first sentence states the primary action, and the second adds essential resource-management context. Every word earns its place.

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 simple one-parameter tool with no annotations and no output schema, the description is complete. It covers purpose, idempotency, when to call, and the resource effect. No critical information is missing for correct 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?

The input schema already provides 100% coverage with 'Session ID to detach.' The description adds minimal extra meaning beyond naming it a 'listener session,' which aligns with the tool's purpose. The baseline of 3 is appropriate because the schema adequately documents the parameter.

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?

The description clearly states the tool's function: 'Detach a listener session.' It names a specific verb (detach) and resource (listener session), and the idempotency note further clarifies behavior. It is distinct from sibling tools like onda_terminal_kill (which would terminate the terminal) and onda_terminal_subscribe (which creates the session).

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

Usage Guidelines4/5

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

The description explicitly says 'Always call this when done to free the ring buffer,' providing clear usage context. It does not mention alternative tools or when not to use it, but the guidance is unambiguous for the resource-cleanup scenario.

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