Skip to main content
Glama

aw.input.abort

Destructive

Discard this pending transfer attempt only; does not cancel the current processing job or delete a completed immutable input. Use jobs.cancel for all pending stages.

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": {
      "session": "<session>",
      "inputId": "<inputId>",
      "attempt": "<attempt>"
    },
    "name": "aw.input.abort"
  }
}

Input Schema

NameRequiredDescriptionDefault
attemptYes
inputIdYes
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuine value by bounding the blast radius — only the pending attempt is discarded, the processing job and immutable input survive. It does not say whether repeated aborts are idempotent, what happens to partially written chunks, or whether the session capability must belong to the attempt's owner.

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?

Two sentences, zero filler, with the scoping constraint front-loaded ahead of the alternative-tool routing. Every clause carries information an agent needs.

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?

For a destructive, three-parameter mutation with no output schema, the description covers the critical safety semantics and the sibling routing. Remaining gaps are secondary: idempotency on repeat calls and the state left behind for the attempt's associated input.

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

Parameters2/5

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

Schema description coverage is only 33%: only 'session' is documented, while 'inputId' and 'attempt' are bare UUID patterns with no explanation. The description adds nothing about any of the three parameters — notably it does not clarify that 'attempt' identifies the specific attempt to discard, which is the core selection mechanism.

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 ('Discard') against a precisely scoped resource ('this pending transfer attempt only'), and immediately bounds it against adjacent operations. An agent can distinguish this from job cancellation and input deletion without opening any 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?

Explicitly names the alternative ('Use jobs.cancel for all pending stages') and states two negative conditions: it does not cancel the current processing job and does not delete a completed immutable input. 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