Skip to main content
Glama
Sign In
GitMem

GitMem

Official
by gitmem-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

log

View past learnings chronologically, showing scars, wins, and patterns. Filter by project, type, severity, or time range.

Instructions

List recent learnings chronologically (like git log). Shows scars, wins, and patterns ordered by creation date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of entries to return (default: 10)
sinceNoDays to look back (e.g., 7 = last week)
projectNoProject namespace (e.g., 'my-project'). Scopes sessions and searches.
severityNoFilter by severity level
learning_typeNoFilter by learning type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.4

TDQS

A4/5.0
Behavior4/5

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

Describes output ordering (chronological by creation date) and content types. No annotations exist, so description adequately covers behavior. Missing details on pagination or side effects, but reads are low risk.

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?

Single sentence with parenthetical simile; no wasted words. Front-loaded with key information.

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?

Complete enough for a simple list tool with well-documented schema parameters. Could note default limit or pagination behavior, but not required.

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 covers 100% of parameters with descriptions. Description does not add any additional meaning beyond what schema already provides.

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?

Clear verb-resource pair ('list recent learnings') with helpful analogy ('like git log') and specific types shown. Distinguishes from siblings like search or recall.

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?

No explicit when-to-use or when-not-to-use guidance. Could mention that for advanced filtering or full-text search, use 'search' instead.

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