Skip to main content
Glama

restore_learning

Restore a lesson deprecated by mistake by clearing its retire or supersede markers so it returns to the active recall set.

Instructions

Un-retire a lesson deprecated by mistake — clears the retire/supersede markers.

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": {
      "learning_id": "<learning_id>"
    },
    "name": "restore_learning"
  }
}

Input Schema

NameRequiredDescriptionDefault
learning_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the concrete mutation (clearing retire/supersede markers), which is useful. It omits whether the call is idempotent, what happens if the lesson is not retired, or any permission prerequisites.

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?

A single tight sentence with the action and state effect front-loaded and no filler. Not padded, though the em-dash clause is the only elaboration offered.

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?

A simple one-parameter mutation with an output schema, so return values need no explanation; the description covers the core action and its state change. Edge-case behavior (invalid or already-active lesson) remains unspecified.

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?

One parameter (learning_id) has 0% schema description coverage and the description adds nothing about it, though the name is self-explanatory and required. Baseline credit for a single obvious identifier is the most this earns.

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?

Specific verb (un-retire) plus resource (a lesson) and the exact state effect (clears the retire/supersede markers) are all stated. It does not, however, tell the agent how this differs from the sibling revert_learning, which sounds functionally adjacent.

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

Usage Guidelines3/5

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

'deprecated by mistake' implies the usage context — undo an erroneous retirement — but there is no explicit when-to-use/when-not-to-use guidance and no named alternative such as revert_learning or update_learning for other kinds of corrections.

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