Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_memos

List your memos (Markdown notes) in reverse chronological order. Returns IDs, titles, tags, and timestamps for quick overview. Use with get_memo to read specific content.

Instructions

List all memos (free-form Markdown notes) belonging to the user, newest first. Returns id, title, tags, and timestamps for each memo, but NOT the full Markdown body — call get_memo to read a specific memo's body. Memos have no status or due date; for actionable tasks use list_todos. Example: returns [{"id":"abc12345-...","title":"Daily notes","tags":["work"],"created_at":"2026-05-27T..."}, ...]. Workflow: typically followed by get_memo(id) when the user wants to read a specific memo's content. Side effects: read-only.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • removedInput schema / description
      Removed value: -"メモ一覧"
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Discloses read-only side effect, return fields (id, title, tags, timestamps, but not body), and ordering (newest first). No annotations to contradict.

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?

Concise yet comprehensive; each sentence adds value (purpose, limitations, example, workflow, side effects). No wasted words.

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?

Fully covers what the tool does, its output, limitations, and relationship to siblings. No output schema needed; description is self-sufficient.

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

Parameters5/5

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

No parameters, so schema coverage is 100% (empty). Description adds value by explaining what the tool returns and behavior, exceeding the baseline.

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 clearly states it lists memos (free-form Markdown notes) for the user, newest first. It distinguishes from siblings like get_memo (for full body) and list_todos (for actionable tasks).

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?

Explicitly tells when not to use (for actionable tasks use list_todos) and workflow hint to call get_memo for full body. No ambiguity.

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