Skip to main content
Glama

remember

Store an observation in Tares's agent-memory lane so it joins correlated reads and resurfaces in the timeline when the same key acts up again.

Instructions

Write an observation back to Tares's agent-memory lane. It becomes a source like any other: joined into correlated reads, so what you learned this incident appears in the timeline next time the same key acts up. memory_type: observation | aggregation | decision.

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": {
      "key": "<key>",
      "content": "<content>"
    },
    "name": "remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
contentYes
memory_typeNoobservation

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful behavioral context that a write becomes a source joined into correlated reads, but it omits permissions, idempotency/overwrite behavior for an existing key, and whether writes are reversible.

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?

Two sentences, front-loaded with the verb and resource, no filler. The memory_type enumeration tacked on the end is slightly abrupt but still earns its place.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and the write's downstream effect is described. But for a 3-param mutation with zero annotation and schema coverage, the definition leaves key/content semantics and permission requirements unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It gives meaning only for memory_type by listing the three values (observation, aggregation, decision) but doesn't define what each means or explain the key/content semantics, leaving two required params undocumented.

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?

States a specific verb and resource: writes an observation back to the agent-memory lane, and names the three memory_type values. It is clear what the tool does, though it doesn't explicitly contrast with the sibling remember_for_project.

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 explicit when-to-use or when-not-to-use guidance; the 'so what you learned this incident appears in the timeline next time' sentence implies a use case (recording incident learnings) but never states conditions, exclusions, or when remember_for_project is preferred.

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