Skip to main content
Glama
hacksurvivor

pathmark

by hacksurvivor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save raw evidence

remember
Idempotent

Save raw searchable evidence with optional tags, source, namespace, and expiry. Use this tool to store unprocessed facts for later recall, while keeping approval-gated conclusions separate.

Instructions

Save raw searchable evidence. Durable intent should use the approval-gated conclusion workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional lowercase-ish tags for later filtering.
textYesMemory text to save.
sourceNoOptional source label, such as repo, thread, or tool name.
expiresAtNoOptional ISO timestamp after which recall excludes this memory.
namespaceNoOptional project, user, or client namespace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.7
    • addedInput schema / properties / expiresAt
      Added value: +{
+  "description": "Optional ISO timestamp after which recall excludes this memory.",
+  "type": "string"
+}
    • addedInput schema / properties / namespace
      Added value: +{
+  "description": "Optional project, user, or client namespace.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover idempotency, non-destructiveness, and write status, so the bar is lower. The description adds useful behavioral context: the stored content is raw and searchable, and durable intent is routed elsewhere. This enriches the agent's understanding beyond the annotation flags.

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 sentences with zero filler. The primary action is front-loaded, and the routing guidance is placed second. Every word earns its place.

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 single-required-parameter save tool, the description plus rich schema and annotations is largely complete. It does not describe the return value or duplicate behavior, but with idempotentHint=true and a straightforward write operation, an agent has enough to invoke it correctly.

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 all five parameters are already documented with their own descriptions. The description does not add parameter-specific meaning beyond what the schema provides, warranting the baseline score of 3.

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 ('Save') and resource ('raw searchable evidence'), making the action unmistakable. It also distinguishes itself from the conclusion workflow for durable intent, which separates it from sibling tools like create_conclusion.

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 tells the agent when not to use this tool ('Durable intent...') and names the alternative ('approval-gated conclusion workflow'). This is an explicit when-not/alternative routing instruction, leaving little to inference.

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

Deploy Server

Other Tools