Skip to main content
Glama

sync

Triggers a manual flomo sync: pull current server notes and tags to your local app and push pending local changes, returning sync statistics. Reports SYNCING if a sync is already running.

Instructions

手动触发同步(等同点击 flomo 界面左下角同步按钮):拉取服务端最新笔记/标签到本地并推送本地待同步修改,返回同步统计。已有同步在进行中时返回 code=SYNCING

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": "sync"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
codeYes
syncedYestrue=本次调用完成一次同步;false=已有同步在进行中(code=SYNCING)
messageYesflomo 返回的同步结果消息
duration_msYes同步耗时(毫秒);SYNCING 时为 null
tag_updatedYes本次同步更新的标签数
pull_successYes拉取服务端数据是否成功;SYNCING 时为 null
push_successYes推送本地待同步修改是否成功;SYNCING 时为 null
updated_memo_countYes本次同步更新的笔记数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers the key behavioral facts: the operation is bidirectional (pull AND push, so it mutates server state), it returns sync statistics, and a concurrent-sync condition yields a specific error, code=SYNCING. That error code is exactly the kind of context an agent cannot get from structured fields. It stops short of saying whether the call blocks until completion, how long it may take, or what happens to conflicting local edits, which keeps it from 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?

One dense but well-ordered sentence structure: purpose first, mechanics second, failure mode last. Every clause adds information — the UI analogue, the two directions of data flow, the return value, and the SYNCING code — with no filler or repetition.

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 not be spelled out, and the description still notes that stats are returned. For a zero-parameter mutation tool with no annotations, the essential facts (it pushes local changes, it reports a concurrent-sync error) are present. Minor gaps remain around blocking behavior and conflict resolution, but nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly presents the call as argument-free.

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 gives a specific verb and resource ('手动触发同步' — manually trigger sync) and defines exactly what that entails: pulling server notes/tags down and pushing local pending changes up. The parenthetical analogy to the flomo UI sync button anchors the concept for an agent that already knows the product, and no sibling tool covers sync, so there is no ambiguity about which tool to pick.

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?

Usage is implied clearly: this is the on-demand trigger, equivalent to pressing the sync button, so an agent calls it when it needs fresh server state or wants pending local edits flushed. There are no explicit when-not conditions (e.g., whether to sync before every read, or whether reads auto-sync), but the sibling list contains no alternative sync mechanism, so the routing decision is unambiguous.

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