mindmap-nimbokit

set_theme

Change the color theme palette of the mind map.

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": {
      "projectId": "<projectId>",
      "theme": "<theme>"
    },
    "name": "set_theme"
  }
}

Input Schema

Name	Required	Description	Default
`theme`	Yes
`projectId`	Yes	The project ID or the full Canvas URL (including the #map=... hash). Passing the full Canvas URL ensures 100% reliable state recovery across turns.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Since there are no annotations, the description must provide behavioral context. It is entirely silent on potential side effects, whether the change is permanent, or if there are state restrictions, making it very low on behavioral disclosure.

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?

The statement is perfectly concise, serving as a simple, single-sentence definition with no extraneous language.

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 description is highly incomplete for a tool that modifies a complex resource. It fails to mention the specific theme names it supports, forcing the agent to rely solely on the schema enum list to understand valid inputs.

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

Parameters2/5

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

The description provides virtually no semantic value beyond restating the function of the tool. Crucial context, such as listing the available theme options (e.g., 'ocean', 'sunset'), is missing from the description, relying entirely on the schema.

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 clearly defines the action ('Change the color theme palette') and the object ('the mind map'). While it doesn't explicitly contrast it with all siblings, its specific focus on 'theme palette' distinguishes it as a styling operation.

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?

The description is purely descriptive and offers no guidance on when to use this tool versus others for styling or when to avoid it. It provides no contextual advice.

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

All mindmap-nimbokit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?