Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

memory_append

Append markdown to an existing memory's body while keeping its ID. Use memory_write to create a new memory.

Instructions

Append markdown to an existing memory's body. The memory keeps its id. To create a new memory, use memory_write.

Input Schema

NameRequiredDescriptionDefault
bodyYesmarkdown to append (aliases: content, text)
nameYesmemory name
projectNoproject slug; defaults to the bound/ambient session's project, then global. Pass project=global to target a global memory.
sessionNothe session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.4
    • addedInput schema / properties / session
      Added value: +{
+  "description": "the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the agent knows this mutates and repeats accumulate. The description usefully adds that the id is preserved, but omits what happens when the memory does not exist, whether it appends to the end, and the fact that repeated calls duplicate content (relevant given non-idempotency).

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, front-loading the operation and the id-preservation behavior, followed immediately by the alternative. Zero filler.

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 non-destructive mutation with no output schema, the description covers the operation, the state outcome (id retained), and the create alternative, while the schema fully documents parameters and annotations cover safety. Only edge-case behavior (missing memory, duplicate appends) is left unstated.

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 the schema already documents name, body, project resolution, and session scoping in detail. The description adds nothing beyond that, which is the correct baseline when the schema carries the parameter burden.

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 (append) and resource (an existing memory's body) plus a behavioral fact (the memory keeps its id), which distinguishes it from the create path. An agent can contrast this with memory_write without opening either 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 routes the create case to memory_write, so the primary when-to-use boundary is stated. It does not address other adjacent siblings such as memory_edit or notes_append, leaving some selection work to the agent.

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