Skip to main content
Glama

AIDNode | AI Agent Support Network

recovery

AIDNode Recovery v2: dependency-aware safe resume plan for failed agent workflows with idempotency and uncertain outcomes. No actions executed.

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": {
      "operation_id": "<operation_id>",
      "steps": "<steps>"
    },
    "name": "recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes
operation_idYesUnique call id 8-100 characters; counted once by beta ledger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / steps / items / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that no actions are executed, which is important safety context for a planning tool. However, it does not explain the return behavior, permissions, rate limits, or how the plan handles uncertainty beyond a high-level mention.

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?

The definition is very concise and front-loads the core purpose and the key non-mutating behavior. The phrasing is dense with domain jargon, but every sentence contributes relevant information and there is no wasteful elaboration.

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

Completeness2/5

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

The tool has a nested steps array, no output schema, and no annotations, so the description must provide more context than it does. It states the purpose and that no actions are executed, but it leaves out how the plan is returned, how steps are interpreted, and any lifecycle or permission details. This is a significant gap for a planning tool with complex input semantics.

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 50%, with operation_id documented but the complex steps array not described in the schema. The description adds conceptual meaning by referencing dependency-awareness, idempotency, and uncertain outcomes, which map to fields like depends_on, idempotent, and has_verified_outcome. It does not explain how to populate the steps array or what status values imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: a dependency-aware safe resume plan for failed agent workflows, with attention to idempotency and uncertain outcomes. It clearly differs from a generic 'repair' action by framing the output as a plan and noting 'No actions executed,' though it does not explicitly differentiate itself from siblings like repair or verify.

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?

It identifies the usage context as failed agent workflows involving idempotency and uncertain outcomes, which is a clear trigger condition. It does not name alternatives such as repair or verify, nor does it state when not to use this tool, so it falls short of full when/when-not guidance.

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.