Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

Download Run Artifact

execution.download_artifact
Idempotent

Download one artifact file.

Local/stdio: saved to NIMBUS_EXPORT_DIR/executions// and its path returned. Hosted gateway: returned inline as contentBase64 (up to 1 MB of base64); larger files point to Nimbus Studio. Nothing is written on the gateway.

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>",
      "artifact_name": "<artifact_name>"
    },
    "name": "execution.download_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesRun that produced the artifact.
artifact_nameYesFile name from execution.artifacts (e.g. "nimbus_lda.pkl").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing environment-dependent behavior: local/stdio writes to NIMBUS_EXPORT_DIR/executions/<id>/ and returns the path, while the hosted gateway returns inline contentBase64 capped at 1 MB and writes nothing, with larger files redirected to Nimbus Studio. This explains why readOnlyHint=false despite the 'nothing written on the gateway' case, and the 1 MB limit is operationally important.

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?

Front-loaded with the one-line purpose, then cleanly splits local versus hosted behavior into short labeled clauses. Every sentence carries distinct information; the 1 MB limit and the redirect behavior both earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter download tool with an output schema and full schema coverage, the description covers the only genuinely ambiguous aspect: what the caller actually receives in each deployment mode. Nothing an agent needs before invoking it is missing.

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 (execution_id and artifact_name, including the filename example) are already documented in the schema. The description adds no syntax, format, or validation meaning beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource: 'Download one artifact file.' The word 'one' distinguishes it from a listing tool like execution.artifacts, but it never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of execution.artifacts (the obvious source of artifact_name) or export alternatives such as bids.export_execution. The dependency is only weakly implied by the schema's reference to execution.artifacts.

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