A
license-
qualityB
maintenanceProvides structured error classification and recovery guidance for MCP agents, turning opaque failures into actionable retry and state information.
16
MIT
RECOVER — Safe Next-Step Decisions After Machine Failures
Server Details
Deterministic next-step decisions after failed API, MCP, automation, or AI-agent actions.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- GSterlingPress/recover-api
- GitHub Stars
- 0
- Server Listing
- recover-api
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlapping purposes. The tool's role is clearly defined and distinct.
Naming Consistency5/5
The single tool name 'recover_decide' follows a consistent verb_noun pattern. There are no other tools to create inconsistencies.
Tool Count2/5
The server has only one tool, which feels too thin for a meaningful server surface. Even a specialized purpose typically benefits from supporting tools like context retrieval or status checks.
Completeness5/5
For its stated purpose of determining safe next-step decisions after failures, the tool covers the full decision space with six possible outcomes. No obvious gaps exist within that narrow scope, as the tool is designed to be the single entry point for this decision.
Available Tools
1 toolrecover_decideAInspect
Use immediately after an API, MCP tool, automation, or agent action fails and before retrying. Especially use after timeouts, 5xx/429 responses, uncertain execution, or any side-effecting action that may already have completed. Returns the safest deterministic next action: RETRY_NOW, WAIT, REPAIR_REQUEST, VERIFY_FIRST, ESCALATE, or ABORT. Do not use before an action or for successful actions.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | Short failure/error message. | |
| method | No | HTTP/action method when known, e.g. GET, POST, PATCH, DELETE. | |
| status | No | Failure HTTP/status code when available. | |
| attempt | No | Current attempt number. | |
| headers | No | Relevant response headers such as Retry-After. | |
| sideEffect | No | True if the failed action could create, modify, send, charge, delete, or otherwise change external state. | |
| maxAttempts | No | Maximum allowed attempts if known. | |
| idempotencyKey | No | True if a valid idempotency key protects a retry. | |
| providerRetryable | No | True only when the provider explicitly marks the failure retryable. | |
| uncertainExecution | No | True when it is unknown whether the action completed before the failure became visible. |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It transparently discloses the tool's behavioral outcome (returns a deterministic next action) and enumerates the possible outputs. However, it does not explicitly state that the tool itself is non-mutating or whether it requires any special authentication, leaving some implicit inference. Overall, it provides good context beyond the schema.
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?
The description is tightly written in four sentences: trigger condition, special cases, return value, and exclusion. Every sentence adds distinct value with no redundancy, making it easy to parse quickly.
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 tool with 10 optional parameters, no output schema, and no annotations, the description covers the primary usage context and return values comprehensively. It does not explain how parameters influence the decision, but the schema already details them. Minor gap: no explicit statement about non-mutating behavior, but the 'Returns' wording implies it. Overall, sufficient for an agent to invoke correctly.
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?
The input schema has 100% description coverage for all 10 parameters, so the schema already fully documents each parameter. The description adds no parameter-specific guidance, which is acceptable given the baseline of 3 for high schema coverage.
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 explicitly states the tool's purpose: to decide the safest next action after a failure, listing the exact possible outputs (RETRY_NOW, WAIT, etc.). It uses a specific verb and resource scope, clearly differentiating it as a recovery decision tool despite having no siblings.
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?
Usage guidelines are explicit and comprehensive: 'Use immediately after... fails and before retrying' and 'Especially use after timeouts, 5xx/429 responses, uncertain execution, or any side-effecting action.' It also states exclusions: 'Do not use before an action or for successful actions.' This provides clear when-to-use and when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceClassifies agent errors and provides clear recovery actions (retry, escalate) with configurable categories and strategies, plus MCP tools for direct agent use.8MIT
- AlicenseAqualityAmaintenanceHelps AI agents avoid repeating known failures by providing deterministic lookup of dead ends for coding errors and country-specific real-world rules.11MIT
- AlicenseBqualityCmaintenanceA debugging workflow plugin for AI coding agents. Turns terminal failures into source-backed fixes via MCP and structured skills.2122MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.