Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

List Pipeline Templates

catalog.templates
Read-onlyIdempotent

List built-in starter pipelines (MI/P300/SSVEP...). catalog.template(id) returns the graph. Each row carries datasetId (catalog id, e.g. "BNCI2014_001" — the id catalog.leaderboard and catalog.datasets use) and paradigm when the template loads a public dataset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "catalog.templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetNoOnly templates on this dataset id (e.g. "BNCI2014_001"); case-insensitive.
paradigmNoOnly templates with this paradigm (e.g. "motor_imagery", "p300", "ssvep").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dataset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only templates on this dataset id (e.g. \"BNCI2014_001\"); case-insensitive."
+}
    • addedInput schema / properties / paradigm
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only templates with this paradigm (e.g. \"motor_imagery\", \"p300\", \"ssvep\")."
+}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuine value by naming per-row fields (datasetId, paradigm) and explaining the catalog-id namespace shared with catalog.leaderboard and catalog.datasets. It says nothing about ordering, pagination, or how many built-in templates exist, and since an output schema exists the return-shape explanation is partly redundant.

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 short sentences, front-loaded with the purpose before the sibling pointer and the row-field note. The parentheses carrying paradigm abbreviations and ID examples are dense but each earns its place; nothing is redundant filler.

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 spelled out, and annotations cover safety. The description supplies the one thing structured fields cannot: that datasetId aligns with the catalog.leaderboard/catalog.datasets namespace. Only pagination or result-size expectations are left unaddressed.

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%, with both filters (dataset, paradigm) fully documented including example values and case-insensitivity, so the baseline is 3. The description's datasetId note clarifies what id style the dataset filter accepts, which is mildly additive, but it does not document filter combination or null behavior.

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 ("List built-in starter pipelines") with concrete paradigm examples, and immediately distinguishes itself from the similarly named sibling catalog.template, which returns the graph. An agent can tell the two apart without opening either 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 pairing of "catalog.templates" for listing with "catalog.template(id) returns the graph" gives a clear discover-then-fetch workflow. It does not explicitly address when to prefer catalog.datasets or catalog.nodes as alternate discovery entry points, so no exclusion guidance is offered.

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

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

Resources