Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

memory_read

Read-onlyIdempotent

Read a shared memory by name from the current project or global fallback, or by id. It accesses server-stored memories only, not local MEMORY.md files.

Instructions

Read a memory by name within the current project (falling back to a global memory of the same name), or directly by id. It reads Seamless memories only -- a name listed in your client's own MEMORY.md (Claude Code's file-based auto-memory) is a local file, not a Seamless memory: open it with your file tools.

Input Schema

NameRequiredDescriptionDefault
idNomemory id (ULID), as carried by events, recall results, and gardener proposals; bypasses name/project resolution
nameNomemory name; pass exactly one of name or id
projectNoproject slug; defaults to the bound session's project
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. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / name / description
      Previous value: -"memory name"New value: +"memory name; pass exactly one of name or id"
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuine context beyond them: the name-lookup falls back to a global memory of the same name, and reads are restricted to Seamless memories only. It omits return shape and error behavior on a missing name, so it is not exhaustive.

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, both front-loaded with the primary behavior and the most likely misfire (treating a local MEMORY.md entry as a Seamless memory). No filler or restatement of the name.

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 read-only tool with no output schema, the description covers access modes, scope, and the local-file distinction, which is what an agent needs to call it correctly. It does not describe the returned memory's shape or what happens when neither name nor id resolves, a minor 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%, so all four parameters (id, name, project, session) are already documented in the schema; the baseline is 3. The description echoes the name-or-id duality but adds no format or scoping detail beyond what the schema states, and never touches project/session.

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 (read) and resource (memory) with two distinct access modes (by name, with global fallback; or by id). It also draws a sharp boundary against a common confusion, distinguishing Seamless memories from client-side MEMORY.md files, so an agent can tell it apart from recall, memory_append, and file tools.

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?

Gives clear selection context: use a name with project scoping/global fallback, or bypass resolution with an id, and redirects local auto-memory files to file tools. It stops short of explicitly contrasting with the sibling 'recall' tool, which is the most likely alternative for retrieval.

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