nimbus-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Stop Stream

stop_stream

Ends a live EEG streaming session safely by disconnecting the device and clearing its idle watchdog, so no timeout fires after an explicit stop.

Instructions

Stop a streaming session and disconnect the device (always safe to call). Also removes the session from the idle watchdog so it cannot fire after an explicit stop.

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": {
      "session_id": "<session_id>"
    },
    "name": "stop_stream"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the operation safe, names the device-disconnect effect, and discloses the non-obvious watchdog side effect that prevents a stale timer from firing after an explicit stop. Gaps remain around behavior when session_id is unknown/expired and whether the call is idempotent, but the disclosed traits are substantive.

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 tightly written sentences with the action and safety guarantee front-loaded and the subtle watchdog behavior second. No filler; every clause adds 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?

An output schema exists, so return values need not be explained, and the description covers the key side effects of a stop operation. It is slightly short on error/edge-case behavior and omits any guidance on sourcing the session identifier, which is the one thing the agent must know to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter session_id is completely undocumented in both schema and description. The description never says what a session_id is or where the agent obtains one (e.g., from start_stream, stream_status, or get_live_session), so it fails to compensate for the coverage gap.

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 specific verb and resource ('Stop a streaming session') plus the concrete side effect ('disconnect the device'), so an agent knows exactly what happens. It is not, however, explicitly differentiated from siblings like cancel_execution or stream_status beyond the self-evident 'stop' semantics.

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?

'always safe to call' and the note about removing the session from the idle watchdog imply this is the correct explicit-termination path, but no alternative (e.g., stream_status for inspection, cancel_execution for a different resource) is named or contrasted. Usage is inferable but never stated as when-to-use vs when-not.

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