@memlane/mcp

list_saves

List saved links and notes in reverse chronological order. Filter by project, topic, type, status, or search text.

Instructions

List saved links and notes, newest first

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_saves"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No
`projectId`	No
`topicName`	No
`kind`	No
`status`	No
`q`	No	Filter by title/summary text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 18, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions ordering ('newest first') but omits pagination details, response format, or any side effects. This is insufficient for an agent to understand tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure. It front-loads the purpose but omits critical details, making it too brief for the tool's complexity (7 parameters, no output schema). It could be improved with bullet points or additional context.

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

Completeness2/5

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

Given the tool has 7 parameters, no output schema, and no annotations, the description is far from complete. It does not explain filtering options, pagination via cursor, or the response structure. A more thorough description is needed for effective use.

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?

The input schema has 7 parameters, but only 'q' has a description. The tool description does not explain any parameters beyond the schema. Since schema coverage is only 14%, the description fails to add meaning to the majority of parameters.

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 it lists saved links and notes with newest first ordering. However, it does not distinguish this tool from sibling tools like search_saves, list_projects, or list_topics, which could cause confusion for the agent.

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 guidance is provided on when to use this tool vs. alternatives such as search_saves for filtered searches or get_save for a single item. The description lacks context for appropriate use.

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

Deploy Server