Skip to main content
Glama

rename_tag

Rename a flomo tag and update its hierarchy using / separators (e.g., Parent/Child) to keep notes organized and tags consistent.

Instructions

重命名标签(层级用 / 分隔,如 开发/Linux)

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": {
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYes新标签名
old_nameYes当前标签名

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses very little: it does not say what happens to memos currently carrying the tag, whether renaming fails when the target name already exists, whether a hierarchy path must pre-exist, or whether the change is reversible. The only behavioral hint is that names are hierarchical paths separated by '/', which is useful but far from complete for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the core action front-loaded and the format hint in parentheses — no waste. It could be marginally clearer by stating explicitly that the path convention applies to both parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and the tool is a simple two-parameter mutation. Still, for a mutation with zero annotation coverage, the definition omits failure modes, side effects on tagged memos, and hierarchy semantics that an agent would need to call it safely.

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%, so the two parameters are already documented as 'current tag name' and 'new tag name'. The description adds genuine meaning beyond that by explaining that tag names are hierarchical paths written with '/', with a concrete example (开发/Linux) — information absent from the schema, even if it does not clarify whether old_name must also be written in full path form.

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 (rename) and resource (tag), which is enough to distinguish it from siblings like list_tags, pin_tag, or create_memo. It stops short of explicitly contrasting with any alternative, but the operation 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says whether this only works on existing tags, whether it is the right tool versus creating a new tag, or what preconditions apply. The parenthetical only gives a naming format, not selection guidance.

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