Skip to main content
Glama
Sign In

kit-memory-demo

by io.github.PeterAtPondo
OverviewDiscussionsAdmin

Finding things

recall

Search Lady Whiskerdown's archive. Use it first for anything Lady Whiskerdown should know. Returns the most relevant entries this key can read; cite each one you use as (Lady Whiskerdown:m#N) with its title.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Leave it unset and the Kit returns the memories that cleared the relevance bar; set it for exactly that many.
queryYesWhat to search for, in natural language
kit_session_idNoYour own session ID from wake; reuse for this conversation. A child or subagent must wake separately, without its parent's ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 10)"New value: +"How many to return. Leave it unset and the Kit returns the memories that cleared the relevance bar; set it for exactly that many."
  3. Changed1 schema field changed
    • addedInput schema / properties / kit_session_id
      Added value: +{
+  "description": "Your own session ID from wake; reuse for this conversation. A child or subagent must wake separately, without its parent's ID.",
+  "maxLength": 160,
+  "minLength": 8,
+  "pattern": "^[A-Za-z0-9:_-]+$",
+  "type": "string"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the full burden and does reasonably well: it discloses the access boundary ("entries this key can read"), the relevance-based result set, and a mandatory citation format agents must follow. It omits whether results are truncated or how ranking is computed, but the read-only nature is clear from "search".

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?

Three sentences, front-loaded with purpose, then usage priority, then the required citation convention. No filler; every clause carries operative information for an agent.

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?

With no output schema, the description usefully sketches the return shape by implying each entry has an identifier (`m#N`) and a title, and it explains the access scope. It leaves the entry payload structure and result truncation unstated, a minor gap for a simple three-parameter search tool.

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 description coverage is 100%, and the parameters (`query`, `limit`, `kit_session_id`) are already documented in detail, including the default-vs-explicit behavior of `limit`. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

"Search Lady Whiskerdown's archive" names a specific verb and resource, which rescues the vague name ("recall") and title ("Finding things"). It does not explicitly contrast with others, though "use it first for anything Lady Whiskerdown should know" implicitly separates it from `remember`, `areas`, and `systems`.

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?

"Use it first for anything Lady Whiskerdown should know" gives a clear default-priority rule that tells an agent when to reach for this tool before others. It stops short of stating exclusions or naming the write-path sibling (`remember`) as the alternative for storing rather than retrieving.

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

All kit-memory-demo toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources