Skip to main content
Glama
Sign In

Nimbus BCI

by io.github.nimbusbci
OverviewDiscussionsAdmin

Delete Upload

data.delete_upload
Destructive

Delete an uploaded file from your account (disk + registry).

Requires confirm=True. Pass the path returned by data.upload (file.path). Only your own uploads can be deleted; missing paths return not-found.

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": {
      "path": "<path>"
    },
    "name": "data.delete_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesUpload path from data.upload (e.g. user_…/file.csv).
confirmNoMUST be true to delete — the explicit user go-ahead.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it discloses that deletion removes both the disk copy and the registry entry, that an explicit confirm flag is required, that only the caller's own uploads are deletable, and that missing paths return not-found. The destructive/destructiveHint=true annotation is reinforced rather than merely restated, and the failure mode is documented.

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?

Four short sentences, front-loaded with the core action and surfaces affected, followed by prerequisites and edge-case behavior. No filler or restated name/title.

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 destructive tool with an output schema and full annotations, the description covers everything an agent needs: what is destroyed, the required confirmation, where the path comes from, scope limits, and the not-found case. Remaining details (return payload, idempotency) are covered by the output schema and annotations.

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%, so both 'path' and 'confirm' are already documented in the schema, including the 'MUST be true' wording. The description restates the same constraints (confirm required, path comes from data.upload) without adding format details such as path normalization or what happens with stale paths. Baseline 3 is appropriate when the schema already carries the parameter meaning.

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 ('Delete an uploaded file from your account') and clarifies the two surfaces affected (disk + registry), which distinguishes it from sibling mutators like execution.delete or project.delete. An agent can tell exactly what object class this operates on without opening the 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?

Gives concrete prerequisites: confirm=True is mandatory, and the path must be the one returned by data.upload (file.path). It also states the ownership constraint ('only your own uploads can be deleted'). It stops short of naming an alternative tool or an explicit 'when not to use' case, but no real alternative exists for this operation.

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