Skip to main content
Glama
Sign In
flomo-mcp-server

flomo-mcp-server

by Jiraiya8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_flomo

Add a note to flomo with Markdown formatting and #tags. Capture ideas via the API for quick logging.

Instructions

向 flomo 添加一条新的笔记/想法。支持 Markdown 格式，可在内容中使用 #标签

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": {
      "content": "<content>"
    },
    "name": "add_flomo"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes要记录的内容，支持 Markdown 格式，可在内容中使用 #标签

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It mentions Markdown and #tags support, but does not disclose any side effects, idempotency, or potential errors. For a simple create tool, this is adequate but not thorough.

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 a single sentence that efficiently conveys the purpose and key features with 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?

Given the tool's simplicity (1 parameter, no output schema, no siblings), the description provides all necessary information: what it does and how it works (Markdown, tags). It is complete for an AI agent to use correctly.

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% for the only parameter, and the tool description essentially repeats the same information. No additional meaning is added beyond what the schema already provides.

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 the action (add) and resource (new note/idea to flomo), with features like Markdown and #tags. Even without sibling tools, the verb-resource pairing is specific and 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?

The context is clear: this tool is for adding notes to flomo. No explicit when-to-use or when-not-to-use is needed given its simplicity, and no alternatives exist. A slight deduction for lacking any notes on prerequisites or limitations.

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