hyperpanes-mcp

Overview Schema Source Related Servers Discussions Admin

Recolor tab

recolor_tab

Sets a tab's color stripe and tint live, saving it with the session; pass a #rrggbb or #rgb value, or null to clear it back to the default or group project color.

Instructions

Set a tab's colour (a stripe and tint on its tab chip), applied live and saved with the session. color is "#rrggbb" or "#rgb"; null clears it back to the default (or, on a pane-group tab, back to the group's project colour, which a manual colour overrides). Address the tab by the tabId list_panes reports.

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": {
      "tabId": "<tabId>",
      "color": "<color>"
    },
    "name": "recolor_tab"
  }
}

Input Schema

Name	Required	Description	Default
`color`	Yes	"#rrggbb" or "#rgb"; null clears the manual colour
`tabId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.20Nov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the change applies live and persists with the session, that null resets to the default, that pane-group tabs fall back to the group's project colour, and that a manual colour overrides that project colour. It omits failure behavior for an invalid tabId and any permission prerequisites.

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?

Front-loaded with the action and effect, then the value format, then the addressing detail — a sensible order with no filler. The nested parenthetical in the null clause is dense but each clause adds distinct information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no annotations and no output schema, the definition covers the missing pieces an agent would otherwise have to guess: valid value forms, reset semantics, override precedence, and ID provenance. Nothing needed to call it correctly is absent.

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

Parameters4/5

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

Schema coverage is 50% — `color` is documented but `tabId` is bare. The description compensates by explaining where tabId comes from (list_panes) and by adding the pane-group fallback nuance for null that the schema does not capture, going beyond the pattern already stated in the schema.

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?

States a specific verb and resource (set a tab's colour) and makes the scope concrete by describing the visible effect — a stripe and tint on the tab chip. The resource word 'tab' alone separates it from recolor_pane and recolor_project without needing to name them.

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

Usage Guidelines4/5

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

Tells the agent how to obtain the required identifier ('the tabId list_panes reports') and spells out the fallback semantics of passing null, including the pane-group case. It does not explicitly say when to prefer recolor_pane or recolor_project, but the resource scoping makes the boundary reasonably clear.

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