Skip to main content
Glama
Sign In

ContextStream

by io.contextstream
OverviewDiscussionsAdmin

Save event to ContextStream

memory_create_event

Save a memory event (decision, insight, achievement, status_update, etc.) to ContextStream. Same as memory(action="create_event"). Prefer session-side tools (session_capture, session_capture_lesson, capture_plan) when the event maps to one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "memory_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesEvent title
contentNoEvent content
event_typeNoEvent type
project_idNoProject ID. Reuse current. UUID.
workspace_idNoWorkspace ID. Reuse current. UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID. Reuse current."New value: +"Project ID. Reuse current. UUID."
    • removedInput schema / properties / project_id / format
      Removed value: -"uuid"
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Workspace ID. Reuse current."New value: +"Workspace ID. Reuse current. UUID."
    • removedInput schema / properties / workspace_id / format
      Removed value: -"uuid"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the description is not the sole carrier. It adds useful routing and aliasing context but says nothing about what is persisted, whether it is deduplicated, or what the call returns.

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?

Two tight sentences with no filler; the core action is front-loaded and the routing guidance follows immediately after.

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 single-required-param create tool with a fully documented schema and no output schema, the definition covers purpose, aliasing and sibling routing adequately. A brief note on persistence or returned identifiers would close the remaining gap.

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 event_type enum is fully enumerated in the schema, so the description's parenthetical type examples (decision, insight, achievement, status_update) duplicate structured data. Baseline 3 applies since no additional parameter semantics are supplied.

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?

States a specific verb+resource (save a memory event to ContextStream) and enumerates representative event types, then anchors it to the sibling entry point memory(action="create_event"). An agent can distinguish this from capture_plan, session_capture and session_capture_lesson without opening any schema.

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?

Explicitly names three alternative tools (session_capture, session_capture_lesson, capture_plan) and gives the routing rule 'prefer them when the event maps to one', plus the memory(action="create_event") equivalence. The condition 'when the event maps to one' is somewhat vague, so it falls short of a full when/when-not spec.

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

All ContextStream toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources