Skip to main content
Glama

edit

Updates one stored memory entry's text, tags, or kind, preserving traceability by superseding the old entry and returning the new ID. Empty fields retain current values.

Instructions

Changes one entry's text, tags or kind.

Under the hood a successor: the changed entry gets a new id, the old one is marked as superseded by it, so what was valid when stays traceable. Fields left empty keep their value.

Returns the new id, as remember does.

Args: id: The entry to change. text: New text; empty keeps the old one. tags: New tags; empty keeps the old ones. kind: New kind; empty keeps the old one. reason: Why - shown on the old entry.

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": {
      "id": "<id>"
    },
    "name": "edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindNo
tagsNo
textNo
reasonNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does substantial work: it discloses the versioning model (new id assigned, old entry marked superseded), why that matters (traceability of what was valid when), and that reason is recorded on the old entry. Gaps remain around permissions, error behavior for invalid ids, and whether superseded entries still surface in recall, but the non-obvious mutation semantics are well covered.

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 core sentence is front-loaded and the supersession explanation follows immediately where it matters most. The docstring-style Args block is slightly redundant in repeating the empty-keeps-value rule, but each line still carries distinct semantic information, so the length is defensible.

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 five-parameter mutation tool with no annotations, the definition covers the essential behavior: identity change, supersession, partial-update semantics, and the audit field. An output schema exists, so the brief return note is sufficient without enumerating return fields; only failure modes and visibility of superseded entries are left unstated.

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

Parameters5/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, and it does: every one of the five parameters is explained, including the critical and non-obvious rule that empty text/tags/kind preserve the existing value rather than clearing it. The reason parameter's destination (shown on the old entry) is also clarified, which is not derivable from the schema at all.

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?

"Changes one entry's text, tags or kind" gives a specific verb plus resource plus the exact mutable fields, so the operation is unambiguous. It is distinguishable in practice from remember (create) and forget (delete), though the description only alludes to that contrast indirectly via "Returns the new id, as remember does" rather than naming the boundary.

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?

Usage context is implied rather than stated: the tool is for modifying an existing entry identified by id, and empty fields preserve prior values, which tells the agent it may send partial updates. There is no explicit when-to-use/when-not guidance, no mention of what to do when the id is unknown, and no reference to a sibling alternative such as remember for creating new entries.

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