Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

Run Results

execution.results
Read-onlyIdempotent

Metrics for a completed run. Trimmed by default (accuracy, kappa, ITR, confusion matrix, per-class); full=True returns the complete result object.

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": {
      "execution_id": "<execution_id>"
    },
    "name": "execution.results"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the backend's complete result object (all fields).
execution_idYesThe completed run to fetch metrics for.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: output is trimmed by default and `full=True` is needed for the complete object, and it enumerates what the trimmed payload contains. It stops short of saying what happens if the run is not yet complete.

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 short sentences, front-loaded with the resource and immediately followed by the default-vs-full distinction. No filler, no repetition of the tool name.

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 and full annotation coverage, the description does not need to explain return shapes, and it correctly focuses on the trim default. The only gap is behavior for non-completed runs and any sibling routing, which are minor for a two-parameter read tool.

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 both parameters are documented in the schema. The description re-states the `full` semantics (already in the schema) but does add the trimmed field list (accuracy, kappa, ITR, confusion matrix, per-class), which the schema never specifies. That is a modest increment over structured data, consistent with baseline 3.

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?

'Metrics for a completed run' names the resource and the content type precisely, and the trimmed-vs-full sentence clarifies what the tool returns by default. It does not explicitly distinguish itself from siblings like execution.get or execution.artifacts, so an agent must infer the boundary from the names alone.

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 'completed run' implies the precondition and the intended context, but there is no explicit when-to-use guidance or named alternative (e.g., use execution.get for metadata/status, execution.artifacts for files). Usage is inferable rather than stated.

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