Ainglish MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

abort_attempt

Close an open attempt without a measurement when a predeclared gate fails. Provide failure type and exact JSON receipt; the server verifies its hash, publishes a copy, and can link to a replacement.

Instructions

AUTH: close your open attempt without a measurement after a predeclared admissibility gate fires. Supply the typed failure and the exact JSON receipt string; the server verifies its hash and publishes a dereferenceable copy. Optionally point to a later replacement attempt.

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": {
      "attempt_id": "<attempt_id>",
      "failed_gate_kind": "<failed_gate_kind>",
      "failed_gate": "<failed_gate>",
      "preflight_receipt_hash": "<preflight_receipt_hash>",
      "preflight_receipt": "<preflight_receipt>"
    },
    "name": "abort_attempt"
  }
}

Input Schema

Name	Required	Description
`attempt_id`	Yes
`failed_gate`	Yes
`failed_gate_kind`	Yes	Machine-checkable class of the failure that stopped the run.
`preflight_receipt`	Yes	The exact UTF-8 JSON object string whose bytes produce preflight_receipt_hash. Stored byte-for-byte and made retrievable.
`successor_attempt_id`	No
`preflight_receipt_hash`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses key side effects: the server verifies the hash, publishes a dereferenceable copy, and optionally links a replacement attempt. It stops short of explaining reversibility or failure behavior, but the main behavioral profile is well communicated.

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 dense sentences each carry weight: purpose, required inputs plus verification behavior, and the optional parameter. There is no filler or repetition of the schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains the purpose, the verification mechanism, and the published outcome, which is helpful for a tool with no output schema and no annotations. However, it omits the precise meaning of failed_gate, the response or return behavior, and whether closing the attempt is irreversible. These gaps matter for an abort operation with six parameters.

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 only 33%, so the description must compensate. It maps 'typed failure' to failed_gate_kind, 'exact JSON receipt string' to preflight_receipt, and 'later replacement attempt' to successor_attempt_id. However, failed_gate remains semantically ambiguous, and attempt_id is only implied, leaving meaningful gaps for a correct call.

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?

The description states a specific verb ('close'), a specific resource ('your open attempt'), and a precise condition ('without a measurement after a predeclared admissibility gate fires'). This clearly distinguishes it from siblings like submit_measurement or mint_attempt, even though no sibling is explicitly named.

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?

The description clearly indicates when to use the tool: after an admissibility gate fires and when there is no measurement to submit. It does not explicitly name alternatives or state when not to use it, but the intended context is clear from the wording and the sibling set.

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