nimbus-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Test Device

test_device

Check an EEG device connection before starting a live stream, validating address or serial settings without starting a session or requiring confirmation.

Instructions

Test a device connection WITHOUT starting a stream (safe, no confirm needed).

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": {
      "device_type": "<device_type>"
    },
    "name": "test_device"
  }
}

Input Schema

Name	Required	Description	Default
`port`	No
`ip_port`	No
`source_id`	No
`ip_address`	No
`device_type`	Yes
`mac_address`	No
`stream_name`	No
`serial_number`	No
`connection_type`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the key trait that no stream is started and no confirmation is required, implying a non-destructive probe. However, it says nothing about authentication requirements, error/failure reporting, or what happens to existing streams, which matters for a 9-parameter device tool.

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?

A single front-loaded sentence with zero filler; the safety constraint is emphasized and placed where it is read first.

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?

An output schema exists, so return values need not be explained, but for a 9-parameter tool with 0% schema coverage the description leaves the agent unable to select the right connection parameters for a given device_type. It is adequate only for the simplest invocation.

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

Parameters1/5

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

Schema description coverage is 0% across 9 parameters, so the description must compensate and it does not. It provides no guidance on device_type (the only required field), nor on which connection identifiers (port vs ip_address/ip_port, serial_number, mac_address, source_id, stream_name) apply to which device types.

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?

States a specific verb and resource ('Test a device connection') and immediately distinguishes itself from the streaming siblings by clarifying it does NOT start a stream. An agent can tell this apart from start_stream/stream_status without opening any schema.

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 parenthetical establishes clear usage context: use this to validate a connection without the side effect of starting a stream, and that it requires no confirmation. It stops short of naming the alternative tool explicitly or stating when-not to use it, but the condition for choosing it is unambiguous.

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