Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

get_memo

Fetch the full Markdown content and metadata of a specific memo by its ID. Use after listing or searching memos to read the body.

Instructions

Fetch the full details of a single memo by ID, including the Markdown content body. Typically called after list_memos or search to read a memo's body. Example: {"id":"abc12345"} returns {"id":"abc12345-...","title":"...","content":"# heading...","tags":[...]}. Side effects: read-only. Errors if the id does not exist or belongs to another user.

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": {
      "id": "<id>"
    },
    "name": "get_memo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemo UUID. Short IDs (first 8 characters of the UUID) are also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / id / description
      Previous value: -"メモID"New value: +"Memo UUID. Short IDs (first 8 characters of the UUID) are also accepted."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description explicitly states 'Side effects: read-only' and 'Errors if the id does not exist or belongs to another user.' This provides good transparency beyond the tool's name.

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 four sentences with no wasted words: purpose, usage context, example, and error conditions. It is front-loaded and efficient.

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?

Given no output schema, the description explains the return includes Markdown content and an example structure. It covers common errors and usage context, making it complete for a single-parameter read tool.

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

Parameters4/5

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

Schema coverage is 100%, and the description provides an example showing the id parameter format and return structure, adding value beyond the schema's description of the parameter.

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 'Fetch the full details of a single memo by ID, including the Markdown content body.' It distinguishes from sibling tools list_memos and search by specifying it is called after them to read a memo's body.

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

Usage Guidelines4/5

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

It says 'Typically called after list_memos or search to read a memo's body.' and provides an example and error conditions. It does not explicitly state when not to use it, but the context is clear.

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