Skip to main content
Glama

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

TableJSON 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
    • 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"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are minimal (only title), so the description carries the burden. It discloses persistence ('Holds until changed or idle past the TTL'), precedence ('explicit area/project args on commit/note/handoff still win'), and the clearing behavior implied by the schema. It does not mention side effects like whether changing focus affects existing memories, but for a state-setting tool this is reasonably transparent.

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 sentences, each earning its place: what the tool does, how it is invoked, and its persistence/precedence behavior. It is front-loaded with the core purpose and avoids redundancy with the schema.

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 state-setting tool with no output schema and minimal annotations, the description covers the essential behavioral context: what the focus affects, how long it lasts, and how it interacts with explicit args. It does not detail the TTL value or what 'idle' means precisely, but that is likely operational detail not required for correct invocation.

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%, so the schema already documents all three parameters. The description adds context about the overall purpose but does not add new meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate because the schema does the heavy lifting.

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 ('Set') and resource ('this operator's write focus'), and clarifies what the focus controls: the knowledge area new memories are stored under and optionally the project. It also distinguishes itself from siblings by noting the wake card's chips call it and that it is callable directly, which helps an agent understand its role relative to tools like wake, remember, and recall.

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

Usage Guidelines5/5

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

The description explicitly says when to use it: to set the write focus for new memories, and notes it is called by the wake card's chips or directly. It also gives clear behavioral guidance: the focus holds until changed or idle past the TTL, and explicit area/project args on commit/note/handoff still win. This effectively tells an agent when this tool is appropriate and how it interacts with other operations.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources