Skip to main content
Glama

learning_history

Retrieve a lesson's earlier versions, newest first, so you can inspect or restore prior text when an update overwrote it.

Instructions

A lesson's earlier versions, newest first — every in-place update keeps the old text.

    Use it when a lesson looks wrong or off-topic (e.g. a bad consolidation merge overwrote it),
    then ``revert_learning`` to put a previous version back. ``None`` if the lesson is unknown.
    

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

Input Schema

NameRequiredDescriptionDefault
learning_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the sort order (newest first), the retention rule (every in-place update keeps the old text), and the failure mode ('None if the lesson is unknown'). It does not state whether the call is read-only or whether any permissions/auth are needed, which is a minor gap for an otherwise read-shaped tool.

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, front-loaded with what the tool returns, then when to use it, then the edge case. The scenario example and the revert_learning pointer each earn their place; no filler or repetition.

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?

For a one-parameter history lookup with an output schema present, the description covers ordering, retention behavior, use case, follow-up action, and the unknown-ID case — enough to call it correctly. It doesn't mention any cap or pagination on version lists, which is the one plausible omission.

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 coverage is 0%, so the single learning_id parameter is undocumented in the schema; the description only implies it identifies a lesson and that unknown IDs yield None. It adds some meaning (failure semantics for a bad ID) but not the identifier's type or where to obtain it. A 3 reflects partial compensation for the coverage gap.

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?

States the specific resource and its ordering: 'A lesson's earlier versions, newest first', which an agent can immediately distinguish from revert_learning, add_learning, or update_learning. It lacks an explicit verb ('returns the version history'), but the noun phrase plus ordering makes the resource scope unambiguous.

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?

Gives an explicit triggering condition ('when a lesson looks wrong or off-topic'), a concrete example scenario (a bad consolidation merge), and names the follow-up action with its sibling tool ('then revert_learning to put a previous version back'). The agent knows both when to call it and what to do with the result.

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