YodMCP

Overview Schema Source Related Servers Discussions Admin

Read memory nodes

memory_read

Read-onlyIdempotent

Retrieve stored facts from an agent's multi-graph memory using semantic similarity or exact item IDs, with optional filters for level, agent, session, or graph type to return scored nodes and neighbor IDs.

Instructions

Retrieve memory nodes by embedding similarity and/or exact item_id, optionally filtered by level, agent, session, or graph kind. Use to recall stored facts. Do not use for reusable plan templates — that is plan_cache_get. Read-only and idempotent. Returns scored items plus neighbor ids. Auth: tool policy gate.

Input Schema

TableJSON Schema

Name	Required	Description
`graph`	No	If set, only return neighbors for this graph kind (temporal/causal/semantic/entity).
`level`	No	Optional level filter: episodic, semantic, or procedural.
`limit`	No	Maximum nodes to return. Default 5.
`query`	No	Free-text query embedded for similarity ranking. Omit when using item_id.
`item_id`	No	Fetch a single node by id instead of searching.
`agent_id`	No	If set, only nodes owned by this agent or unscoped nodes.
`session_id`	No	If set, only nodes in this session or unscoped nodes.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.5.0Aug 26, 2026

addedInput schema / properties / agent_id / description

Added value: +"If set, only nodes owned by this agent or unscoped nodes."

addedInput schema / properties / graph / description

Added value: +"If set, only return neighbors for this graph kind (temporal/causal/semantic/entity)."

addedInput schema / properties / item_id / description

Added value: +"Fetch a single node by id instead of searching."

addedInput schema / properties / level / description

Added value: +"Optional level filter: episodic, semantic, or procedural."

addedInput schema / properties / limit / description

Added value: +"Maximum nodes to return. Default 5."

addedInput schema / properties / query / description

Added value: +"Free-text query embedded for similarity ranking. Omit when using item_id."

addedInput schema / properties / session_id / description

Added value: +"If set, only nodes in this session or unscoped nodes."

First observedv0.4.0Aug 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: the auth gate requirement and the return shape ('scored items plus neighbor ids'). No contradiction with 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?

Three tight sentences with no filler: purpose first, then routing guidance, then safety/return/auth context. Every sentence earns its place.

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

Completeness5/5

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

With 7 optional parameters, an output schema, and complete annotations, the description adds the missing auth context and a concise return-shape summary. An agent has enough information to invoke the tool correctly and route around the main alternative.

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 coverage is 100%, so the schema already documents each parameter thoroughly. The description restates the filter dimensions and retrieval modes but adds little semantic detail beyond what the schema provides; the query-vs-item_id exclusion is already in the schema.

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?

Opens with a specific verb and resource ('Retrieve memory nodes'), names the retrieval modes (embedding similarity, exact item_id), and lists the optional filters. It clearly distinguishes this read tool from memory_write/memory_delete and explicitly separates it from plan_cache_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('Use to recall stored facts') and names the alternative for reusable plan templates ('plan_cache_get') with a direct exclusion ('Do not use...'). An agent can route to the correct tool without inspecting sibling definitions.

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