Skip to main content
Glama

add_learning

Record a durable decision, mistake, or how-to lesson with optional repo scope and detail so future sessions can recall and apply it.

Instructions

Record a durable lesson so future sessions recall it. type: decision|mistake|howto.

    ``statement`` is the lesson in one crisp sentence; ``detail`` the why/correction/better-way;
    ``scope`` the repo it applies to as its git remote ``owner/repo`` (e.g. ``the-dsvolk/qmx``)
    — omit it for a global lesson. A bare repo name is mapped to the one known ``owner/repo``
    it matches, and rejected with the options if it matches none or several.
    

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": {
      "type": "<type>",
      "statement": "<statement>"
    },
    "name": "add_learning"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
scopeNo
topicNo
detailNo
statementYes
importanceNo

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, and it does disclose one real behavioral trait: bare repo names are resolved against known owner/repo values and rejected with the candidate options when ambiguous or unknown. It also signals durability across sessions. However, it says nothing about what happens on duplicate lessons, whether the call is idempotent, or what a successful record returns.

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 front-loaded first sentence states the purpose, followed by parameter-specific notes grouped logically. Formatting with backticks is readable and there is little filler, though the awkward line breaks and trailing whitespace make it slightly messier than necessary.

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 six-parameter mutation tool with no annotations and no output schema, this covers the essential mechanics: required fields, the type vocabulary, and the scope resolution failure mode. The gaps around topic, importance, and duplicate handling keep it from being fully complete.

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 description must compensate, and it partially does: it supplies the type enum values (which the schema does not constrain), explains statement and detail as one-sentence lesson vs. rationale, and gives format plus omission rules for scope. Two of the six parameters, topic and importance, are never mentioned, leaving their meaning entirely undefined.

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 opens with a concrete verb+resource: 'Record a durable lesson so future sessions recall it.' That makes the write-and-persist intent clear and separable from read-oriented siblings like recall and lessons. It stops short of naming any sibling or scope boundary explicitly, so it is clear but not fully differentiated.

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?

Usage is implied through 'durable lesson' and the type taxonomy (decision|mistake|howto), which tells an agent what kinds of content belong here. There is no explicit guidance on when to use this versus update_learning or deprecate_learning, nor any statement about deduplication or when a lesson should instead be parked.

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