Skip to main content
Glama

search_memos

Search flomo notes by keyword across note content and tags with case-insensitive matching, returning results sorted by update time descending to help find relevant memos.

Instructions

按关键词搜索笔记(匹配正文与标签,大小写不敏感,结果按更新时间降序)。flomo 无远程搜索接口,每次调用全量拉取后本地过滤;翻页时传 next_cursor 且 keyword 保持不变

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": {
      "keyword": "<keyword>"
    },
    "name": "search_memos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数(mode=all 时每页最多 100 条,超出按 100 执行)
cursorNo翻页游标(上次返回的 next_cursor,必须配合首次搜索的同一 keyword)
keywordYes搜索关键词(匹配正文与标签,大小写不敏感)

Output Schema

NameRequiredDescriptionDefault
countYes本次返回条数
memosYes
matchedYes匹配总数
scannedYes本次实际扫描笔记数
completeYesfalse=触达 40 页扫描上限,结果可能不全
next_cursorNo存在即匹配结果未取完,原样传入下次调用(keyword 不变)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does a lot: it discloses that no remote search API exists, that every call performs a full fetch with local filtering (a real latency/volume cost), and that results are ordered by update time descending. It does not cover permissions or rate limits, which keeps it short of a 5.

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 dense sentences with zero waste: the search semantics come first, then the implementation constraint and the pagination rule. Every clause carries information an agent needs.

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 explanation, and the description covers the non-obvious behavior (full fetch plus local filter, stable keyword across pages). What remains uncovered are the limit semantics and permission requirements, which is a minor gap for a 3-parameter read tool.

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 coverage is 100%, so every parameter is already documented. The keyword semantics in the description duplicate the schema, and the cursor explanation (pass next_cursor with the same keyword) is nearly identical to the schema's own cursor description, so it adds little beyond 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 names a specific verb plus a resource (搜索笔记) and pins down the matching semantics (正文与标签、大小写不敏感) and the result ordering (按更新时间降序), so an agent can tell it apart from list_memos without opening either schema. It adds the core local-filtering caveat that defines this tool.

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 concrete guidance on pagination: pass next_cursor and keep keyword unchanged. What's missing is explicit direction on when to prefer this tool over list_memos or list_tags, and there are no stated exclusions.

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