Memos MCP Server

list_memos

List memos across connected Memos instances. Filter by state, CEL expressions, and sorting to quickly find relevant notes.

Instructions

List memos from one or all connected Memos instances.

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": "list_memos"
  }
}

Input Schema

Name	Required	Description
`state`	No	Filter by state
`filter`	No	CEL filter expression (e.g., "tag == \"important\"")
`orderBy`	No	Order by field (e.g., "display_time desc")
`instance`	No	Instance name to query. If not specified, queries all instances.
`pageSize`	No	Number of memos to return (default: 20, max: 1000)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral weight. 'List' signals a read-only operation and 'from one or all connected instances' adds multi-instance scope, but the description does not mention pagination behavior, return format, or any implications of querying all instances. It is adequate but not rich.

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 a single front-loaded sentence with no filler. Every word earns its place, and the most important scoping information ('one or all connected instances') is stated immediately.

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 list operation with five optional parameters, a rich schema, and no output schema or annotations, the description is nearly sufficient. It identifies the resource and scope, while the schema covers the parameters; the main gap is the lack of guidance about return structure or behavior when querying all instances.

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 five parameters are already documented with meanings and defaults. The description adds no parameter-level detail beyond the schema, which matches the baseline 3 for high-coverage schemas.

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 uses a specific verb ('List') and a precise resource ('memos'), and scopes it to 'one or all connected Memos instances.' This clearly separates it from sibling tools like get_memo (single memo) and list_instances (instances, not memos), so an agent can tell what it does without opening the schema.

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 operation itself implies when to use it — when memos need to be retrieved — but the description never states exclusions or points to alternatives such as get_memo for a single memo. It gives the scope (one/all instances) but not explicit when-to-use-versus-sibling guidance.

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

Deploy Server