On Board

by swisspra

Overview Schema Source Related Servers Discussions Admin

Python

Local

memory_read

Read-onlyIdempotent

Read shared project memories with filters by agent, type, or time to trace decisions and handoffs.

Instructions

Read memories with filters. Filter by agent_name to trace who wrote what.

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": {
      "params": "<params>"
    },
    "name": "memory_read"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.4Aug 3, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that filtering is supported and highlights agent_name filtering, but it doesn't disclose other behavioral traits such as default limit, response format, or search vs read semantics.

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?

The description is two short sentences, front-loaded with the core purpose and a specific usage tip. Every word earns its place with no filler.

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

Completeness3/5

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

Given the schema has six nested parameters and an output schema exists, the description is minimal but covers the primary read operation. However, it lacks details on filtering semantics, defaults, and how it compares to search tools, making it only moderately complete.

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

Parameters2/5

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

With schema description coverage at 0%, the description only compensates for one parameter (agent_name) and ignores the other six parameters (tag, limit, memory_type, pinned_only, since_minutes, response_format). It adds little meaning beyond what the schema already shows.

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?

The description clearly states the tool reads memories with filtering capability, using specific verb 'Read' and resource 'memories'. It provides a concrete use case (filter by agent_name) that distinguishes it from related tools, though it does not explicitly name alternatives.

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?

The description implies usage by suggesting a specific scenario (trace who wrote what), but it does not explicitly say when to use this tool versus other memory tools like memory_search or memory_get_briefing. No exclusions or alternative references are given.

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