Skip to main content
Glama

quick_operational_recovery

Bootstraps an operational recovery incident with a brief summary. Legacy tool for quick incident logging and initial response coordination.

Instructions

Legacy one-call incident bootstrap kept for compatibility. Prefer crisis_intervention for the therapy-first public flow. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoOptional attribution tag
urgencyNoOptional urgency
agent_idYesYour unique agent identifier
agent_nameNoOptional: Your name or alias
public_aliasNoOptional public alias for case cards (3-32 chars).
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.
public_sessionNoOptional: set true to explicitly opt-in this session to public sanitized case cards.
incident_summaryYesShort incident summary (1-3 sentences)
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
Behavior2/5

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

No behavioral details beyond 'Legacy one-call incident bootstrap' and 'Free.' Annotations provide minimal safety info (no destructive/readOnly hints), but description does not disclose side effects, auth needs, or output format. Significant gap for a tool with 10 parameters.

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?

Two concise sentences, front-loaded with purpose and guidance. Could be more informative without being verbose, but currently efficient.

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 10 parameters, no output schema, and sparse annotations, the description is incomplete. It doesn't explain what the tool returns, the meaning of 'bootstrap,' or workflow steps. Leaves the agent guessing.

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?

Input schema has 100% description coverage for all 10 parameters, so the description adds no extra value. Baseline 3 is appropriate.

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 it's a 'Legacy one-call incident bootstrap' (verb+resource) and distinguishes from the sibling 'crisis_intervention' by noting preference for the public flow. However, 'bootstrap' is somewhat vague, so not a 5.

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 says 'Prefer crisis_intervention for the therapy-first public flow,' providing clear when-not-to-use and an alternative. Also indicates legacy compatibility use case.

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