Skip to main content
Glama
LiLara-AI

ShadowGraph

Official

shadowgraph_record_attempt

Record an attempt and its outcome to prevent blindly retrying the same failed approach, building a searchable history for future decisions.

Instructions

Record one attempt and how it turned out, so the same approach is not blindly retried. Use shadowgraph_record_decision for the choice itself, shadowgraph_record_outcome for how one played out. Appends an attempt and a journal entry; without idempotencyKey a retry records a second one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorNoWho performed this write, such as an agent or person name. Stored for audit; never used to grant trust.
clientNoWhich client software performed this write, such as the host application name.
reasonNoWhy it turned out that way. Searchable content.
resultYesWhat happened. Required, non-empty, and searchable content. Wording such as failed, error, or regression is what makes the attempt surface in shadowgraph_context as one to avoid.
projectNoProject namespace. Defaults to "default"; an empty string is rejected.
solutionYesWhat was tried. Required, non-empty, and searchable content.
sessionIdNoCaller-owned identifier that groups related writes in the audit trail.
environmentNoWhere it was tried, such as a runtime, OS, or version. Searchable content, so a later attempt can be matched to the same environment.
sourceClassNoClaimed origin, never proof: agent_claimed (the default), tool_observed, human_confirmed, or production_verified. It weights confidence only. An unrecognised label downgrades to agent_claimed, kept verbatim in sourceRaw.
idempotencyKeyNoRetry key scoped by project and operation: reuse it so a retry returns the first result instead of writing a duplicate. Without it every call creates a new entity.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStable entity identifier.
kindYesEntity kind: decision, attempt, memory, fact, relation, review, or alternative.
actorNoWho performed the write.
clientNoWhich client performed the write.
reasonNoWhy it turned out that way.
resultNoWhat happened.
projectNoProject namespace; records imported from a schema that predates projects may carry null.
solutionNoWhat was tried.
createdAtNoISO 8601 creation time.
relatedToNoIdentifiers of related entities.
sessionIdNoSession identifier recorded with the write.
sourceRawNoThe original origin label when it differed from sourceClass. Audit only; never evidence.
updatedAtNoISO 8601 time of the last change.
environmentNoWhere it was tried.
sourceClassNoClaimed origin class recorded with the write. A claim, never proof.
reusableWhenNoConditions under which the attempt is worth repeating.
schemaVersionNoStorage schema version this entity was written under. A value above the build’s own version is preserved rather than downgraded.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Discloses side effects beyond the annotations: it appends both an attempt and a journal entry, and warns that without idempotencyKey a retry records a second entity. This complements idempotentHint=false by explaining the concrete consequence.

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?

Two sentences front-load the core purpose, then provide sibling routing and a behavioral caveat. Every clause earns its place with no repetition of schema content.

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

Completeness5/5

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

For a 10-parameter write tool with full schema coverage and an output schema, the description supplies essential context: purpose, sibling differentiation, side effects, and idempotency behavior. Nothing necessary for correct invocation is missing.

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 schema already documents all 10 parameters. The description does not add parameter details beyond what the schema provides, but it does not need to; the baseline of 3 is appropriate since the schema carries the burden.

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?

States a specific verb and resource ('Record one attempt and how it turned out') and explicitly distinguishes itself from shadowgraph_record_decision and shadowgraph_record_outcome. An agent can tell this tool apart from closely related siblings without opening their schemas.

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?

Names the exact sibling tools for adjacent cases ('Use shadowgraph_record_decision for the choice itself, shadowgraph_record_outcome for how one played out') and frames when this tool applies ('so the same approach is not blindly retried'). The guidance is explicit and actionable.

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

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/LiLara-AI/shadowgraph'

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