Skip to main content
Glama
Sign In

kit-memory-demo

by io.github.PeterAtPondo
OverviewDiscussionsAdmin

focus

focus

Set this operator's write focus: the knowledge area new memories are stored under, and optionally the project being worked on. The wake card's chips call this; it is also callable directly. Holds until changed or idle past the TTL; explicit area/project args on commit/note/handoff still win.

Input Schema

NameRequiredDescriptionDefault
areaNoKnowledge-area slug for new writes. Empty string or omitted clears to General (no area routing).
projectNoProject slug for new writes. Empty string clears.
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
    • 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"
+}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations beyond the title, the description carries the behavioral burden and discloses key stateful traits: the focus holds until changed or idle past the TTL, and explicit per-call arguments still win. It does not describe error behavior, permission requirements, or return values, but for a non-destructive focus-setting tool it provides meaningful operational context.

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?

The description is three tight sentences with no wasted wording. It front-loads the core action and then adds persistence and override behavior in a logical order.

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?

For a simple state-setting tool with full parameter schema coverage and no output schema, the description covers purpose, caller context, persistence, and precedence. It could additionally specify the TTL duration or failure behavior, but nothing critical for calling it correctly 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 100%, so the schema already documents the parameters. The description adds useful meaning by explaining that area and project determine routing for new memories and that explicit arguments on commit/note/handoff take precedence, which is not expressed in the schema.

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 specific verb and resource: 'Set this operator's write focus: the knowledge area new memories are stored under, and optionally the project being worked on.' This clearly distinguishes the tool from storage/retrieval siblings like remember, recall, and areas by explaining that it configures routing for future writes rather than performing those writes.

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?

It gives clear usage context: wake card chips call it, and it is also directly callable. It also explains that the setting persists until changed or TTL expiry, and that explicit area/project arguments on commit/note/handoff override it. It lacks an explicit when-not-to-use statement, but the alternatives and precedence rules are clear.

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