Skip to main content
Glama

get_memo

Retrieve a single flomo note's full HTML and plain-text content by slug; use it before updating to fetch the current content.

Instructions

获取单条笔记全文(HTML 与纯文本)。update_memo 前先调用本工具取当前内容

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

Input Schema

NameRequiredDescriptionDefault
slugYes笔记 slug

Output Schema

NameRequiredDescriptionDefault
slugYes
tagsYes
created_atYes
updated_atYes
content_htmlYes原始 HTML,update_memo 需基于此修改回写
content_textYes纯文本(已解码 HTML 实体)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload (HTML and plain text) and implies a read-only fetch via 'get', but says nothing about permissions, behavior on a missing slug, or whether content is truncated. Adequate but with clear gaps for a tool with zero annotation coverage.

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?

Two short clauses, zero filler, with the core purpose front-loaded and the pre-call guidance appended. Every sentence earns its place.

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?

An output schema exists, so return values need no further explanation, and the description still notes both content formats. For a simple one-parameter read, the only missing piece is error/empty-result behavior.

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% with a single 'slug' parameter already documented in the schema. The description adds no format, casing, or lookup-failure semantics beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource (retrieve the full text of a single memo) and specifies the returned formats (HTML and plain text), which separates it from list/search siblings. It stops short of naming an explicit contrast tool, but 'single memo' vs. listing tools is unambiguous.

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 gives a concrete pre-condition: call this before update_memo to fetch current content. That is a clear when-to-use rule tied to a named sibling. It does not state when not to use it (e.g., when only metadata or a listing is needed), which keeps it out of the top band.

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