Skip to main content
Glama

Compose a CSS gradient

bpj_palette_gradient_css
Read-onlyIdempotent

Arrange palette colors into equidistant CSS gradient stops at a supplied angle.

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>",
      "angle": "<angle>"
    },
    "name": "bpj_palette_gradient_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYes
paletteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful behavior by saying the stops are equidistant and angle-controlled, but it does not state the return format or how palette ordering is handled.

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?

It is a single front-loaded sentence with no filler. The operation and both inputs are stated immediately.

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?

The tool is simple, but with no output schema and no parameter descriptions, the definition should say more about the expected return (such as a CSS string) and the palette JSON format. It is minimally usable but leaves meaningful gaps for confident invocation.

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 compensate, but it only refers to 'palette colors' and a 'supplied angle.' It does not clarify that palette is a JSON array of hex colors, its max length, or the angle bounds, leaving format details to the schema titles and constraints.

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 ('Arrange') and resource ('palette colors into equidistant CSS gradient stops') and states the angle input. It is clear, but it does not distinguish this from sibling gradient/color tools such as bpj_color_linear_gradient.

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 gives no when-to-use or when-not-to-use guidance, no alternatives, and no prerequisites. The agent must infer that this tool is for generating a CSS gradient from a palette.

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.