Skip to main content
Glama

Generate CSS palette variables

bpj_palette_css_variables
Read-onlyIdempotent

Write a validated palette as sequential CSS custom properties in a root rule.

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": {
      "palette": "<palette>"
    },
    "name": "bpj_palette_css_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
paletteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that output is sequential custom properties emitted inside a root rule, which is genuinely useful shape information. The verb 'Write' is mildly ambiguous against readOnlyHint (it means emit text, not mutate state), and no ordering/duplication behavior or exact output formatting is described.

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?

One front-loaded sentence with no filler or repetition; every word contributes to the purpose. It is arguably too terse rather than too verbose, but there is no structural waste to penalize.

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?

For a single-parameter generator with no output schema and zero schema description coverage, the description should explain the accepted input encoding and what the emitted CSS looks like. Instead it leaves the JSON-array-of-hex requirement and output shape entirely implicit. Only the annotations and the parameter title partially fill the gap.

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?

Schema description coverage is 0%, so the description must carry the input semantics, and it does not. It never explains that the single 'palette' parameter is a JSON-serialized hex color array, nor mentions the 1500-character limit or expected ordering. 'Validated palette' is the only hint, and it leaves the exact accepted format to guesswork.

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 states a concrete verb and output artifact: writing a validated palette as sequential CSS custom properties inside a root rule. That is far more specific than the title alone and implies a text-generation output. It does not, however, distinguish itself from near siblings such as bpj_palette_gradient_css or bpj_css_hex_shorthand, so an agent must guess which palette-to-CSS tool to pick.

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?

There is no when-to-use guidance, no mention of prerequisites such as needing a validated palette first, and no named alternative. The single word 'validated' hints that input must already pass validation but never says so explicitly or points to the validating tool. An agent gets no routing signal beyond the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.