Nimbus BCI

Plots.Erp

plots.erp

Idempotent

ERP butterfly figure from epoched data: one subplot per class, all channel means (thin) + across-channel mean (bold), time-locked to the trial event. Shows whether class-conditioned evoked structure exists BEFORE training anything.

Input Schema

Name	Required	Description	Default
`mode`	No	Pack split to load: training \| evaluation \| all (source=dataset).	all
`path`	No	Upload path (source=upload) or absolute local path (source=local).
`save`	No	Also write the PNG to NIMBUS_EXPORT_DIR/plots/ and return its path.
`source`	Yes	"dataset" (MOABB pack), "upload" (path from data.upload), or "local" (absolute path, local backend only).
`dataset`	No	MOABB dataset id, e.g. "BNCI2014_001" (source=dataset).
`subject`	No	Subject id, e.g. "S01" (source=dataset).
`max_channels`	No	Channels drawn per class subplot (default 16, max 64).

Output Schema

Name	Required	Description
`ok`	Yes
`meta`	No	Figure sidecar. foundation.compare includes results/best/skipped (also as a JSON text content block).
`title`	No
`mimeType`	No
`savedPath`	No	Set when save=true.
`sizeBytes`	No	Set when save=true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedOutput schema / properties / meta / description

Added value: +"Figure sidecar. foundation.compare includes results/best/skipped (also as a JSON text content block)."

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "meta": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "mimeType": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "savedPath": {
+      "description": "Set when save=true.",
+      "type": "string"
+    },
+    "sizeBytes": {
+      "description": "Set when save=true.",
+      "type": "integer"
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

AddedOct 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true, and readOnlyHint=false, so the safety and idempotency profile is mostly covered. The description adds useful context about the figure's content and its pre-training diagnostic purpose, but does not disclose additional behavioral traits such as save behavior, authentication needs, or rate limits.

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 tight sentences with no wasted words. It front-loads the plot type and data source, then immediately gives the diagnostic purpose, making it easy to parse quickly.

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. Combined with 100% schema description coverage and annotations covering safety traits, the description provides enough context for an agent to understand the tool's purpose. It could be richer by noting the source variants or save option, but those are adequately captured in the schema.

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%, meaning all seven parameters are already documented in the schema. The description does not add any parameter-level meaning, which is acceptable but not value-adding; the baseline of 3 applies when schema coverage is high.

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 gives a specific verb and resource: it creates an ERP butterfly figure from epoched data, detailing the subplot structure, channel means, and time-locking. It is clear what the tool does, but it does not explicitly distinguish itself from sibling plotting tools such as plots.dataset or plots.confusion.

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 states a clear use context: to inspect whether class-conditioned evoked structure exists BEFORE training anything. It does not name alternatives or say when not to use this tool, so it falls short of the explicit routing found in the top-scoring examples.

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

All Nimbus BCI 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.