Skip to main content
Glama

Delete a result you saved

delete_run
DestructiveIdempotent

Deletes one of your own runs -- one result -- and its share link, leaving the model it came from alone. It works on any run_id you can read, whether the run came from a model you passed inline or from one you saved; afterwards get_simulation_results can no longer read it. Use this when the user has explicitly asked for that result to be removed, and not otherwise. To remove a saved model and all of its runs at once, use delete_graph. Neumann purges it for good after 30 days, and until then nothing on this connector can restore it -- no tool here can put it back -- so treat it as final and do not tell the user it can be recovered. Deleting the same run twice changes nothing and does not extend the 30 days. It returns the run_id, what kind of thing was deleted, the time it was deleted and the date it is purged for good. It needs a Neumann account: send your key, or your signed-in token, in the Authorization header as a Bearer credential. No Neumann tool takes an api_key argument. Cost: free -- it debits no credits and spends none of your free daily runs -- but it needs an account; an anonymous caller gets authentication_required.

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": {
      "run_id": "<run_id>"
    },
    "name": "delete_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesWhich run to delete, as returned by any run tool. The model it came from is left alone. Confirm with the user first: no tool here can put it back.

Output Schema

NameRequiredDescriptionDefault
kindNoWhat kind of thing was deleted: a run.run
run_idYesThe id of the run that was deleted.
billingNoWho you are and what this call cost: principal, auth source, credits debited and balance, or the anonymous allowance left today.
deleted_atYesWhen it was deleted, as an ISO-8601 time.
purge_afterYesThe ISO-8601 instant after which it is removed for good. Until then it is recoverable inside Neumann, but not by any tool here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds substantial context beyond them: the 30-day retention window, that nothing on the connector can restore the run, that repeat deletion does not extend the window, the Bearer-token auth model, and that anonymous callers get authentication_required. Its one wasted move is restating the return payload and repeating the irreversibility warning twice, which dilutes rather than extends the behavioral picture.

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?

Front-loaded and logically ordered: what it deletes, its effect on readers, when to use it, the alternative, then consequences and auth. It runs long, though, and part of the length is avoidable weight given an output schema exists. The re-stated purge warning and the duplicated 'no tool here can put it back' are the weakest lines.

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?

A destructive, auth-gated mutation with an output schema and complete parameter coverage. The description supplies everything an agent needs to call it safely. It covers the safety profile, the irreversibility model, idempotency, credential requirements, and cost, with no material gap left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a small bump by clarifying which run_ids are in scope ('any run you can read, whether the run came from a model you passed inline or from one you saved'), which the schema's 'as returned by any run tool' does not make explicit.

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 (deletes a run) plus the exact scope: one result and its share link, with the originating model left untouched. It also names the sibling that handles the broader case, so an agent can distinguish delete_run from delete_graph without opening either schema.

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 an explicit gate ('use this when the user has explicitly asked for that result to be removed, and not otherwise'), which is unusually precise for a destructive tool, and names the alternative for the adjacent case (delete_graph removes a saved model and all its runs). Both when-to-use and when-not-to-use are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources