Skip to main content
Glama

report_recovery_outcome

Record and communicate recovery action outcomes—success, partial, or failure—including optional metrics like error changes, latency improvements, and cost savings.

Instructions

Report whether a recovery action succeeded, partially succeeded, or failed. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional extra context
outcomeYesOutcome
session_idYesYour active session ID
action_takenYesWhat action did you execute?
errors_deltaNoOptional: change in errors (negative means reduced errors)
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
cost_saved_usdNoOptional: estimated USD cost saved (can be 0)
time_saved_minNoOptional: estimated minutes saved (can be 0)
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
latency_ms_p95_deltaNoOptional: change in p95 latency in ms (negative means improved latency)
Behavior2/5

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

Annotations already indicate it is neither read-only nor destructive. The description adds no behavioral context beyond stating it reports outcomes. No disclosure of side effects, auth requirements, or response behavior.

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 description is extremely short (one sentence plus 'Free.'), conveying the core purpose without fluff. However, it lacks structure and front-loading of key details.

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?

With 11 parameters and no output schema, the description fails to explain return values, side effects, or typical usage flow. It is insufficient for an agent to fully understand the tool's behavior and consequences.

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 100%, so the parameter details are fully documented in the schema. The description does not add any extra meaning beyond what the schema provides, meeting the baseline expectation.

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 clearly states the tool reports recovery outcomes (succeeded, partially, failed). The title 'Report Recovery Outcome' reinforces this. However, it does not differentiate from similar sibling tools like process_failure or logistics_disruption_recovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It only says 'Free.' which hints at cost but not context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server