Skip to main content
Glama

revert_learning

Restore a lesson from its revision history, defaulting to the latest saved revision. Saves the current text as a new revision first so the restore can itself be undone.

Instructions

Restore a lesson from its history; revision_id defaults to the latest revision.

    The current text is saved as a new revision first, so a revert can itself be reverted.
    Returns the restored lesson, or ``None`` if ``learning_id`` does not exist.
    

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": "revert_learning"
  }
}

Input Schema

NameRequiredDescriptionDefault
learning_idYes
revision_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the current text is first saved as a new revision, making reverts reversible, and that the tool returns None for a nonexistent `learning_id`. It omits permission or authorization requirements and says nothing about what happens with an invalid `revision_id`.

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?

Three short sentences with no filler; the core action and default are front-loaded and the reversibility note follows naturally. Every sentence adds information an agent would otherwise lack.

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?

An output schema exists, so return values need not be fully explained, yet the description still usefully flags the None case. For a two-parameter mutation with no annotations, it is nearly complete, with only error and permission behavior left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain the parameters, and it does: `revision_id` defaults to the latest revision and `learning_id` drives the existence check that yields None. It still does not state whether `revision_id` must belong to the given lesson or what format/range it accepts.

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 gives a specific verb and resource: restore a lesson from its history, with a clear notion of revisions. It does not distinguish itself from the sibling tool `restore_learning`, so an agent cannot tell which of the two to pick without further inspection.

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?

It states the default behavior when `revision_id` is omitted, which implicitly tells the agent when the parameter matters. However, it never says when to use this tool instead of `restore_learning`, `update_learning`, or `learning_history`, and it gives no preconditions.

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