Skip to main content
Glama

Shorten a CSS hex literal

bpj_css_hex_shorthand
Read-onlyIdempotent

Check each channel for repeated nibbles and produce the shortest exact hex literal.

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

Input Schema

NameRequiredDescriptionDefault
colorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 closed-world scope, so safety is covered. The description adds one genuinely useful behavioral fact beyond them — that shortening is exact (lossless), not an approximation — but says nothing about what is returned when no channel has repeated nibbles or how case/prefix are handled.

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 tight sentence with no filler, and the core outcome ('shortest exact hex literal') comes last after the mechanism. It is efficient, though slightly abstract wording ('check each channel for repeated nibbles') costs a little immediate clarity.

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?

This is a small deterministic transform with no output schema and rich annotations, so the bar is modest and the description covers the core semantics. However, it omits the no-op case (input returns unchanged) and input formatting rules, which are the details an agent actually needs to call it correctly.

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% and the description never mentions the single `color` parameter, so it adds no meaning beyond the bare schema title 'Six-digit hex color' and maxLength 7. It does not clarify whether the '#' prefix is required, whether 7-character input is expected, or whether already-shortened values are accepted, which are exactly the ambiguities an agent would hit first.

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 transformation: examine each channel for repeated nibbles and emit the shortest exact hex literal, which clearly distinguishes this from siblings like bpj_replace_literal or bpj_palette_css_variables. It stops short of naming the canonical 6-digit-to-3-digit case or the input form, so the resource is clear but not fully pinned down.

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 or when-not-to-use guidance at all: nothing tells the agent to reach for this instead of a general literal replacement or palette tool, and no preconditions are stated. Usage can only be inferred from the one-line purpose.

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.