Skip to main content
Glama
Sign In
MemKernel

MemKernel

by varadganjoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memkernel_note

Record a short-lived scratchpad note for cooperating coding agents, automatically compacted by garbage collection over time.

Instructions

Record an ephemeral scratchpad note (compacted by GC over time).

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": {
      "note": "<note>"
    },
    "name": "memkernel_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses that notes are subject to garbage collection over time, which is a key behavioral trait beyond the schema. However, it omits return behavior, note size limits, whether notes are queryable, and interaction with memkernel_trigger_gc.

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 front-loaded sentence with zero waste. Every word (Record, ephemeral, scratchpad, GC) adds meaning.

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?

An output schema exists, so return values need not be explained. For a one-parameter tool, the description covers the essential lifecycle trait (ephemeral, GC'd) that the schema cannot express. Minor gaps around size limits or queryability are acceptable given the tool's simplicity.

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 description coverage is 0%, so the description must compensate. It clarifies the note is an ephemeral scratchpad, distinguishing the content from durable logs or decisions. The single required string parameter's semantics are adequately implied by the verb 'Record' plus the scratchpad context.

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 a specific verb and resource: write an ephemeral scratchpad note. Clearly distinguishable from siblings like memkernel_append_decision or memkernel_log_execution by its ephemeral/scratchpad nature. Lacks explicit sibling differentiation but the purpose is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this versus memkernel_append_decision (durable decisions) or memkernel_log_execution. The 'ephemeral' hint implies transient use cases but doesn't state exclusions or alternatives.

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