Skip to main content
Glama

pin_tag

Pins a specified flomo tag so it remains prioritized for quick access in your tag list.

Instructions

置顶标签

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": {
      "tag": "<tag>"
    },
    "name": "pin_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes标签名

Output Schema

NameRequiredDescriptionDefault
tagYes
pinnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only states an operation name. It does not say whether pinning is idempotent, whether it fails when the tag is already pinned, what ordering/visibility effect it has, or whether it requires auth — all material 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.

Conciseness2/5

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

At four characters it is certainly short, but this is under-specification rather than conciseness — there is no structure, no front-loaded scope statement, and no sentence that earns its place because no explanatory sentence exists.

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

Completeness2/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 described. However, for a zero-annotation mutation tool the definition should at least convey the effect of pinning and failure conditions; the name alone leaves the agent guessing about side effects.

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% (the single `tag` string param is documented as "标签名"), so the schema already carries the parameter meaning. The description adds nothing beyond that, which is the baseline-3 case rather than a deficiency.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"置顶标签" is simply the Chinese rendering of the tool name pin_tag — a verb+resource pair with no elaboration. It does not distinguish this tool from siblings like unpin_tag or rename_tag, nor does it explain what pinning a tag actually accomplishes in the product.

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, no prerequisites (must the tag already exist?), and no mention of the obvious alternative unpin_tag for the inverse operation. The agent must infer the context entirely from the name.

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