Skip to main content
Glama
Sign In
Waymark

Waymark

by SerjMihashin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memory_read

Read-only

Retrieve a specific memory node by its UUID or by combining project ID and name slug to access stored context for AI agent handoffs.

Instructions

Read a single memory node by id or by project+name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoMemory node UUID
nameNoMemory node name slug
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already provide readOnlyHint=true. The description merely restates 'Read' without adding further behavioral details (e.g., error handling, auth requirements, or limitations). No contradiction, but no added transparency beyond annotations.

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?

Single sentence, front-loaded with purpose and key usage. Zero waste, 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 read tool with readOnlyHint annotation, the description covers the essential lookup modes. While it omits return format and not-found behavior, the tool is straightforward and the description is sufficiently complete.

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

Parameters4/5

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

The description clarifies the idiomatic usage patterns: either 'id' alone or 'name' + 'project_id' together. This adds meaningful context beyond the schema, which marks parameters as optional without explaining the combinatorial constraint.

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 precisely states 'Read a single memory node by id or by project+name.' This clearly identifies the verb and resource, and distinguishes it from sibling tools like memory_search (which likely returns multiple results) and memory_write (which mutates).

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?

No explicit guidance on when to use this tool versus alternatives like context_get or memory_search. The description implies usage for known identifiers but does not specify prerequisites or exclusions.

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