Skip to main content
Glama

crystal_lesson

Record, resolve, and list lessons learned across crystals to prevent repeated friction and agent amnesia. Capture root causes and recommended actions so agents avoid cognitive regression.

Instructions

Record, resolve, or list lessons learned across crystals to prevent cognitive regression, repeated friction, and agent amnesia.

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": {
      "action": "<action>"
    },
    "name": "crystal_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoLesson identifier (e.g. lesson-1; required for resolve/dismiss; optional for record)
actionYesAction: record (capture lesson), resolve (mark resolved/actioned), dismiss, or list
statusNoFilter status for list action (optional: open, actioned, dismissed)
actor_idNoEntity ID performing the action (optional, defaults to agt_mcp)
crystal_idNoTarget crystal ID (required for record and resolve; optional for list)
root_causeNoRoot cause analysis of the friction (optional)
action_summaryNoSummary of resolution action taken (optional for resolve)
observed_frictionNoDescription of the observed friction or failure pattern (required for record)
recommended_actionNoActionable pattern, rule, or remediation to prevent recurrence (optional for record)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It explains the high-level intent but does not disclose mutation effects, whether resolve/dismiss are reversible, permission requirements, or what list returns, which matters for a tool with both read and write actions.

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 a single front-loaded sentence with no structural clutter. The phrase about preventing cognitive regression is somewhat promotional but does not materially detract from conciseness.

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?

For a nine-parameter, multi-action tool with no annotations and no output schema, the description is too thin. It does not clarify action-specific requirements, return behavior for list, or consequences of resolve/dismiss, leaving significant gaps beyond what the schema covers.

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 input schema already documents all nine parameters and their enums. The description adds no parameter-level detail beyond naming the actions, which is acceptable at baseline when the schema does the heavy lifting.

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 a specific resource and set of verbs: 'Record, resolve, or list lessons learned across crystals.' An agent can understand the tool's core purpose, but the description does not differentiate it from sibling tools such as crystal_triage or crystal_archive.

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 gives no explicit guidance on when to use this tool versus alternatives, nor does it state exclusions or prerequisites. Usage is only implied by the action verbs and purpose statement, leaving the agent to infer selection criteria from the schema alone.

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