Skip to main content
Glama
fitz2882

learned-experience

by fitz2882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Recall past experience

recall
Read-onlyIdempotent

Check past solutions before investigating a problem to avoid repeating mistakes. Returns ranked fixes, avoid-lists, and confidence scores from prior episodes and rules.

Instructions

Check whether this problem (or a similar one) has been solved before. Call BEFORE investigating. Returns ranked hits with fix, avoid-list and confidence. Exact error text in signals enables deterministic matching; semantic + lexical search catches near matches. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindsNoRestrict to 'episode' or 'rule' records
limitNoMax hits (default 5)
contextNoTags: language, framework, tool, OS
problemYesOne-line generic description of the problem
signalsNoExact error messages, failing commands, symptoms
min_scoreNoDrop non-exact hits below this score (default 0.45)
environmentNo
include_historyNoInclude superseded records for explicit historical investigation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • addedInput schema / properties / environment
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "platform": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "product": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "project": {
+      "maxLength": 160,
+      "type": "string"
+    },
+    "version": {
+      "maxLength": 80,
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / include_history
      Added value: +{
+  "description": "Include superseded records for explicit historical investigation",
+  "type": "boolean"
+}
    • changedInput schema / properties / min_score / description
      Previous value: -"Drop non-exact hits below this score (default 0.35)"New value: +"Drop non-exact hits below this score (default 0.45)"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds meaningful behavior beyond annotations: it explains that exact error text in `signals` enables deterministic matching while semantic and lexical search catch near matches. It also confirms 'Read-only,' consistent with the readOnly and idempotent hints. No contradictions.

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?

Four short sentences with no filler. The primary purpose is front-loaded, followed by the key usage directive, return shape, and a precise note on matching behavior. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only memory-search tool with a rich schema and no output schema, the description covers purpose, when to call, return contents, matching semantics, and safety. The parameter detail lives in the schema, so nothing essential is missing.

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 high (88%), so the schema carries most parameter documentation. The description adds value by highlighting the behavioral role of `signals` ('Exact error text enables deterministic matching') beyond its schema field description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Check whether this problem (or a similar one) has been solved before.' It also explains what is returned (ranked hits with fix, avoid-list, and confidence), which clearly differentiates it from sibling tools like record, inspect, or stats.

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

Usage Guidelines4/5

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

The instruction 'Call BEFORE investigating' is explicit and actionable, telling the agent exactly when to invoke this tool. It does not enumerate alternatives or exclusions, but the strong temporal guidance and search-oriented purpose make usage context clear.

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

Deploy Server

Other Tools