rainkeeper

Overview Schema Source Related Servers Discussions Admin

update_collection

Modify a collection's details by changing its title, visibility, or colour. Provide optional updates like a hex colour or public status.

Instructions

Update a collection's title, visibility, or colour. color is a hex string e.g. '#ff0000'.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "update_collection"
  }
}

Input Schema

Name	Required	Description	Default
`color`	No
`title`	No
`public`	No
`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.1/5.0

Behavior2/5

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

Annotations absent, so description carries full burden. Only states 'update' which implies a write operation, but no mention of side effects, permissions, reversibility, or error conditions. Output schema present but not referenced.

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?

Very concise single sentence, no redundant information. Front-loaded with key action and fields. Efficient use of words.

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?

Given 4 parameters, 1 required, and no annotations, the description is minimal. Lacks details on partial updates, error handling, or authorization. Output schema partially compensates, but overall incomplete for safe invocation.

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 coverage is 0%, so description compensates partially. Provides example for 'color' hex string, but only lists 'title' and 'visibility' without additional constraints or formatting. No description for 'collection_id' despite being required.

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?

Clearly states it updates a collection's title, visibility, or colour. Distinguishes from sibling tools like create_collection and delete_collection. Minor mismatch: description says 'visibility' while schema uses 'public', but synonymous.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., create_collection, get_collection). Usage is implied by the verb 'update', but no context or exclusions provided.

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