rainkeeper

by simonives

Overview Schema Source Related Servers Discussions Admin

Python

Remote

move_raindrop

Move a bookmark to a different collection. Provide the bookmark ID and target collection ID.

Instructions

Move a single bookmark to a different collection. Explicit tool for clarity.

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": {
      "raindrop_id": "<raindrop_id>",
      "target_collection_id": "<target_collection_id>"
    },
    "name": "move_raindrop"
  }
}

Input Schema

Name	Required	Description	Default
`raindrop_id`	Yes
`target_collection_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations provided, and the description only states the basic action without disclosing any behavioral traits like idempotency, error handling, or side effects.

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?

The description is very concise with one sentence, but it is efficient and front-loaded; however, it may be too brief to convey necessary details.

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?

The tool has two simple parameters and an output schema, but the description lacks context on return values, error conditions, or prerequisites, making it incomplete for a thorough understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description adds no meaning to the parameters ('raindrop_id', 'target_collection_id') beyond their names.

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 ('move'), resource ('bookmark'), and target ('collection'), and distinguishes from bulk counterparts with 'single bookmark' and 'Explicit tool for clarity'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies a single-item use case, and the sibling tool 'bulk_move_raindrops' provides contrast, but there is no explicit when-to-use or when-not-to-use guidance.

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