Skip to main content
Glama
gitmem-dev

GitMem

Official
by gitmem-dev

create_learning

Create entries in institutional memory to document scars, wins, and patterns from past sessions, enabling AI agents to recall and learn from prior experiences.

Instructions

Create scar, win, or pattern entry in institutional memory. Frame as 'what we now know' — lead with the factual/architectural discovery, not what went wrong. Good: 'Fine-grained PATs are scoped to one resource owner'. Bad: 'Should have checked PAT type first'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesFrame as a knowledge discovery — what we now know. Lead with the factual insight, not self-criticism.
domainNoDomain tags
projectNoProject namespace (e.g., 'my-project'). Scopes sessions and searches.
keywordsNoSearch keywords
severityNoSeverity level (required for scars)
scar_typeNoScar type (process, incident, or context). Defaults to 'process'.
descriptionYesDetailed description. Include the architectural/behavioral fact that makes this retrievable by domain.
applies_whenNoWhen this pattern applies
learning_typeYesType of learning
problem_contextNoProblem context (for wins)
counter_argumentsNoCounter-arguments for scars (min 2 required)
solution_approachNoSolution approach (for wins)
source_linear_issueNoSource Linear issue
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, permission requirements, or effects of duplicates. For a creation tool, this is a significant gap.

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 description is concise at ~50 words and front-loaded with the core purpose. It could be slightly more structured but is efficient overall.

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

Completeness3/5

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

With 13 parameters and no output schema, the description omits important context such as the relationship between learning_type and other fields (e.g., severity for scars). It does not explain required vs optional parameters fully.

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 100%, but the description adds value by explaining the tone for 'title' and 'description' (factual insight, no self-criticism) and grouping learning types. This goes beyond the schema's field descriptions.

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 clearly states 'Create scar, win, or pattern entry in institutional memory,' specifying the verb (create) and resource (learning entry). It differentiates from sibling tools like 'create_decision' by explicitly naming the learning types.

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 description provides guidance on framing (lead with factual discovery, not what went wrong) and gives good/bad examples. However, it does not explicitly state when not to use this tool or compare it to alternatives like 'record_scar_usage'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitmem-dev/gitmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server