Skip to main content
Glama
Sign In

kit-memory-demo

by io.github.PeterAtPondo
OverviewDiscussionsAdmin

Reading presence

presence

Read live Lady Whiskerdown facet presence within the requested window.

Input Schema

NameRequiredDescriptionDefault
toNoDelivery address of a live session, taken from this tool's own facets list. Sends instead of reading. The address is issued by the server and bound to the session that holds it; a session id is not an address and will not be accepted as one.
scopeNoWhich conversations to include. Defaults to work, which withholds personal threads.
messageNoAt most 400 characters, delivered in full in that session's next presence check or memory-read footer, quoted as another session's words. Sending means queued, not confirmed read. Nothing wakes or spawns; quiet sessions are refused and unread messages expire after 30 minutes.
kit_session_idNoYour own session ID from wake; reuse for this conversation. A child or subagent must wake separately, without its parent's ID.
window_minutesNoLive window in minutes. Defaults to 30. Maximum 1440.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / window_minutes / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / window_minutes / minimum
      Added value: +-9007199254740991
  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. Changed2 schema fields changed
    • addedInput schema / properties / message
      Added value: +{
+  "description": "At most 400 characters, delivered in full in that session's next presence check or memory-read footer, quoted as another session's words. Sending means queued, not confirmed read. Nothing wakes or spawns; quiet sessions are refused and unread messages expire after 30 minutes.",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Delivery address of a live session, taken from this tool's own facets list. Sends instead of reading. The address is issued by the server and bound to the session that holds it; a session id is not an address and will not be accepted as one.",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Which conversations to include. Defaults to work, which withholds personal threads.",
+  "enum": [
+    "work",
+    "personal",
+    "general",
+    "all"
+  ],
+  "type": "string"
+}
  5. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations supply only a title, so the description carries the full burden, and it under-delivers: it frames the tool purely as a read while the schema reveals a send mode with queueing semantics, 30-minute message expiry, refusal of quiet sessions, and no wake/spawn behavior. None of that side-effect profile appears in the description, so an agent reading only the prose would not anticipate the mutation path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence is admirably short and front-loaded with the verb, so it passes the conciseness test. However, the economy comes at the cost of the tool's second mode and any usage context, so the brevity reads as under-specification rather than precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with a dual read/send behavior, no output schema, and no meaningful annotations, a single read-only sentence is not enough. Key facts an agent needs before calling — the send mode, session requirements, delivery guarantees — exist only in the schema, leaving the description incomplete relative to the tool's complexity.

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 coverage is 100% and the parameter descriptions are unusually thorough (address binding, scope defaults, 400-char limit, window default and max), so the schema does the heavy lifting. The description adds only the loose notion of a 'requested window', which maps to `window_minutes` but adds no format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb+resource ('Read ... presence') within a time window, which is understandable in outline, but the phrasing 'Lady Whiskerdown facet presence' is domain jargon that doesn't tell an agent what data actually comes back, and it silently omits that the same call can send a message via the `to`/`message` parameters. It does not differentiate itself from siblings such as wake, recall, or focus.

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?

There is no guidance on when to use this tool versus wake, recall, or focus, and no mention of prerequisites such as needing a session id from wake. The only positional hint is 'within the requested window', which is a scope statement, not usage guidance.

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