move-note
Relocate a note to a specific notebook. Provide the note GUID, notebook GUID, and confirmation to complete the move.
Instructions
移笔记
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | ||
| confirm | Yes | ||
| notebookGuid | Yes |
Relocate a note to a specific notebook. Provide the note GUID, notebook GUID, and confirmation to complete the move.
移笔记
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | ||
| confirm | Yes | ||
| notebookGuid | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose any behavioral traits such as whether moving a note is destructive, requires confirmation, or changes notebooks. The confirm parameter suggests a destructive or irreversible action, but this is not explained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short (one word), but this is under-specification rather than effective conciseness. It does not earn its place as it provides no additional information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a move operation with three required parameters and no annotations or output schema, the description is completely inadequate for an AI agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain any of the three required parameters (guid, confirm, notebookGuid). The purpose of the confirm parameter is unclear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description is '移笔记', which is a direct translation of the tool name 'move-note'. This is a tautology, providing no additional clarity about what the tool does beyond the name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like clone-note or delete-note. The description does not mention any context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArchChuan/yinxiang-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server