Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

Protocol Session Status

protocol.session_status
Read-onlyIdempotent

Live snapshot of a protocol deploy session: the scheduler block / session progress + threshold state (under protocol) beside the telemetry window (recent indicators, quality, stats).

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": {
      "session_id": "<session_id>"
    },
    "name": "protocol.session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoHow many recent predictions to include (1-200, default 50).
session_idYesThe deploy session to inspect (from start_assignment).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds that the result is a "Live snapshot" and outlines the returned sections, but it does not explain freshness guarantees, refresh behavior, or other runtime traits beyond the annotation coverage.

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?

It is a single front-loaded sentence with no filler and communicates the snapshot contents efficiently. The slash-and-parenthetical structure is somewhat dense, but still readable and appropriately sized.

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 annotations covering safety and an output schema covering return structure, the description supplies enough context to understand the tool's role. Its main gap is not clarifying when to choose this over adjacent protocol and stream status tools.

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%, and the schema already documents session_id and window clearly. The description does not add parameter-specific meaning, such as the distinction between the session being inspected and the prediction window size.

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 clearly states that this is a live snapshot of a protocol deploy session, with specific content areas: scheduler block, session progress, threshold state, and telemetry window. It does not explicitly distinguish itself from siblings such as protocol.list, protocol.export_stats, or stream.status, so it falls short of a 5.

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 "Live snapshot" implies this is for inspecting a current session state, but there is no explicit guidance on when to use it instead of protocol.list, protocol.export_stats, execution.get, or stream.status. Usage is therefore inferable but not directly 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