Skip to main content
Glama

kit-memory-demo

by io.github.PeterAtPondo
OverviewDiscussionsAdmin

Reading presence

presence

Read live Lady Whiskerdown facet presence within the requested window.

Input Schema

TableJSON 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. 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. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A3.8/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. The description and parameter details disclose several behavioral traits: reading is the default, but providing 'to' sends instead; messages are queued not confirmed; quiet sessions are refused; unread messages expire after 30 minutes; nothing wakes or spawns. This goes well beyond the schema and annotations.

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

Conciseness4/5

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

The main description is a single concise sentence that front-loads the core purpose. The parameter descriptions are detailed but not bloated, and each sentence earns its place by adding behavioral context. Slightly verbose parameter descriptions, but overall well-structured.

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 tool with 5 parameters, no output schema, and minimal annotations, the description plus parameter details cover the key behavioral aspects: reading vs sending, queueing semantics, expiration, session requirements, and scope filtering. It doesn't describe return values, but with no output schema that's a minor gap given the rich parameter-level context.

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 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it clarifies that 'to' is an address from this tool's own facets list, that sending means queued not confirmed, and that 'scope' defaults to work which withholds personal threads. This adds value beyond the schema's own descriptions.

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?

The description states a specific verb ('Read') and resource ('live Lady Whiskerdown facet presence') within a requested window. It clearly identifies the tool's core function, though it doesn't explicitly differentiate it from sibling tools like 'recall' or 'remember' in the description itself.

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

Usage Guidelines3/5

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

The description implies usage context ('live presence within the requested window') but provides no explicit guidance on when to use this tool versus alternatives like 'recall' or 'remember'. The parameter descriptions add some context (e.g., 'Sends instead of reading'), but the main description lacks explicit when/when-not 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
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