Skip to main content
Glama

Dimension Value Colors Set

dimension_value_colors_set
Destructive

Assigns fixed colors to dimension values across charts, merging by value unless replace is enabled, so categories keep consistent colors.

Instructions

Resource > Manage dimension value colors: fixed color per dimension value in every chart (when the theme colors by dimension values). Merges by value unless replace. Max 1500 values. Journalled, verified, restorable.

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": {
      "colors": "<colors>"
    },
    "name": "dimension_value_colors_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYes
dry_runNo
replaceNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses real behavioral traits: merge-by-value semantics unless 'replace' is set, a hard cap of 1500 values, and that changes are 'journalled, verified, restorable'. The restorability note meaningfully softens the destructive hint for an agent deciding whether to proceed. It stops short of saying exactly what 'replace' nullifies or how partial failures behave.

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?

Four dense, front-loaded sentences with no filler; the resource path, effect, merge rule, limit, and recoverability all appear in order of decision importance. The telegraphic final fragment ('Journalled, verified, restorable.') reads as notes rather than prose but still carries information.

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?

An output schema exists, so return values need no coverage, and the destructive/merge/cap/recovery details cover the core risk profile. Still missing for a mutation tool: what 'dry_run' actually returns (preview vs. live write), what 'report_id' is for, and any permission requirement. Adequate but with visible holes.

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 description coverage is 0%, so the description must carry parameter meaning. It explains the 'colors' payload ('fixed color per dimension value') and the 'replace' flag ('merges by value unless replace'), and adds a 1500-value cap absent from the schema. But 'dry_run' (default true) and 'report_id' receive no explanation at all, which is a material gap for a mutating tool.

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 names a specific verb ('Manage') and a precise resource ('dimension value colors'), then defines the effect: 'fixed color per dimension value in every chart (when the theme colors by dimension values)'. That scope statement is unambiguous. It lacks any pointer to a sibling alternative, so it falls short of a 5.

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 parenthetical '(when the theme colors by dimension values)' establishes a conditional applicability rule, which is genuinely useful. However, there is no explicit when-not guidance, no mention of when to prefer this over per-chart styling elsewhere, and no prerequisite/permission note. Usage is implied rather than directed.

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

Deploy Server

Other Tools