Nimbus BCI

Plots.Leaderboard

plots.leaderboard

Idempotent

Leaderboard bar chart for one dataset: accuracy with 95% CI whiskers, best first; BYO python_model submissions highlighted in a distinct color. The visual companion to catalog.leaderboard. On the pretrained_few_trial track the figure also includes the classical LOSO baseline as a muted side panel for comparison.

Input Schema

Name	Required	Description	Default
`save`	No	Also write the PNG to NIMBUS_EXPORT_DIR/plots/ and return its path.
`track`	No	"within_session" (curated 5-fold), "crossSubject" (LOSO, curated + BYO submissions), or "pretrained_few_trial" (the efficiency track: LOSO at the protocol's fixed per-subject trial budget — the figure also includes the classical LOSO baseline as a muted side panel for comparison).	within_session
`dataset_id`	Yes	Dataset to chart, e.g. "BNCI2014_001" (see catalog.leaderboard).

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"
+}

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / track / description

Previous value: -"\"within_session\" (curated 5-fold) or \"crossSubject\" (LOSO,\ncurated + BYO submissions)."New value: +"\"within_session\" (curated 5-fold), \"crossSubject\" (LOSO,\ncurated + BYO submissions), or \"pretrained_few_trial\" (the\nefficiency track: LOSO at the protocol's fixed per-subject\ntrial budget — the figure also includes the classical LOSO\nbaseline as a muted side panel for comparison)."

AddedOct 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=true and destructiveHint=false, and the description adds rendering behavior (distinct color for BYO submissions, muted LOSO side panel on pretrained_few_trial) that helps the agent anticipate the output. It does not, however, note that save=true writes a PNG to disk (only the schema says so), which is the one non-read-only behavior implied by readOnlyHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core deliverable (chart type, metric, ordering) before the companion/sibling note and the track caveat. Slightly wordy around the pretrained_few_trial clause but nothing is wasted.

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?

With an output schema present, the description needn't explain return values, and it adequately conveys what the figure shows and how track changes it. The only gap is acknowledging the save-to-disk side effect, which the schema covers instead.

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 coverage is 100%, so all three parameters are already documented, and the description's note about the pretrained_few_trial side panel largely duplicates the track parameter's own schema text. Baseline 3 is correct when structured fields carry the parameter detail.

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?

Names a specific artifact (leaderboard bar chart for one dataset) with concrete visual details (accuracy with 95% CI whiskers, best first, BYO submissions highlighted), and explicitly positions itself as 'the visual companion to catalog.leaderboard', distinguishing it from that sibling and other plots.* tools.

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 phrase 'visual companion to catalog.leaderboard' implies when to reach for this tool versus fetching leaderboard data, and the track description explains context, but there is no explicit when/when-not guidance or statement of prerequisites for producing the figure.

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.