Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bulk_delete_runs

Delete up to 500 runs irreversibly. Requires explicit confirmation to prevent accidental loss of traces and cost history.

Instructions

Delete up to 500 runs at once. IRREVERSIBLE — unlike archiving, deleted runs do not come back, and their traces and cost history go with them. Prefer bulk_archive_runs unless a human has explicitly asked for deletion. Returns counts of succeeded and failed; a partial failure is possible.

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": {
      "runIds": "<runIds>",
      "confirm": "<confirm>"
    },
    "name": "bulk_delete_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdsYesThe run ids to delete.
confirmYesMust be true. Destructive and irreversible — ask your human first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. Covers irreversibility, loss of traces and cost history, and possibility of partial failure.

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 concise sentences, no redundant information, effectively structured with warnings and guidance.

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?

Given the tool's destructive nature and no output schema, the description covers key points: batch limit, irreversibility, alternative, and partial failure. Differentiates well from many sibling tools.

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% with parameter descriptions. Description adds context: 'IRREVERSIBLE' for confirm, and mentions return counts. Adds value beyond schema.

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?

Clearly states the action 'Delete up to 500 runs at once' with resource (runs) and scope (up to 500). Distinguishes from sibling tools like bulk_archive_runs and other delete operations.

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?

Explicitly advises preferring bulk_archive_runs unless human explicitly requests deletion, and warns about irreversibility and partial failure.

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

Deploy Server

Other Tools