Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

Delete Run

execution.delete
Destructive

Permanently delete one of your finished runs (completed/failed/cancelled) with its results. Running runs must be cancelled first (409 nimbus.execution.delete_not_terminal). Owner only.

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.delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMUST be true to delete — the explicit user go-ahead.
execution_idYesThe run to delete (from execution.run/execution.list).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: it discloses that results are destroyed along with the run, that the operation is state-gated, the exact error semantic, and the authorization constraint. This is exactly the what-gets-destroyed / auth-needs context the annotations cannot express.

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?

Three short sentences with zero filler: scope first, precondition second, authorization third. Every clause carries decision-relevant information.

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 the essential risk/precondition information is all there. It does not state side effects on related records (e.g., leaderboard submissions or exported artifacts tied to the run), a minor gap for a permanent deletion.

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 both parameters are documented in-schema, including the confirm=MUST-be-true requirement and where execution_id comes from. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ("Permanently delete ... runs") and narrows the scope to finished runs with the states enumerated (completed/failed/cancelled). An agent can distinguish it from execution.cancel and execution.get without opening either schema, since the terminal-state precondition is spelled out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (only finished runs), an explicit alternative for the non-qualifying case ("Running runs must be cancelled first" — i.e., use execution.cancel), and names the exact failure code (409 nimbus.execution.delete_not_terminal). The "Owner only" clause adds the permission precondition an agent needs before attempting the call.

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