Skip to main content
Glama

Composite an alpha foreground

bpj_alpha_over_background
Read-onlyIdempotent

Composite a foreground over an opaque background using encoded sRGB channels.

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>",
      "other": "<other>",
      "opacity": "<opacity>"
    },
    "name": "bpj_alpha_over_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
otherYes
opacityYes

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 this as a read-only, idempotent, closed, non-destructive operation, so the safety profile is covered. The description adds the useful colorimetric constraint that compositing happens in encoded (non-linear) sRGB and that the background must be opaque. It says nothing about the result format, clamping behavior, or invalid-hex handling, so it stays at a modest level.

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?

A single front-loaded sentence with no filler, and the key operation is stated first. It is perhaps too terse for the gaps it leaves, but the dimension penalizes only clarity and unnecessary wording, not scope.

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 three-parameter required tool with no output schema and 0% schema coverage, the description is not sufficient. An agent still cannot tell the return value (presumably a hex string) or the parameter-to-role mapping, and these gaps are not covered anywhere else in the definition.

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 carries the full burden, and it does not compensate. It never says which parameter is the foreground and which is the background, nor does it explain that 'opacity' acts as the alpha channel; the phrases 'foreground' and 'background' in the sentence are not mapped to 'color' or 'other'.

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?

States a specific verb and resource: composite a foreground over an opaque background. It also hints at the color space ('encoded sRGB channels'), which is more precise than the title. It does not, however, relate itself to any sibling such as bpj_choose_monochrome_foreground, so an agent must infer the boundary from names alone.

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 statement of prerequisites, and no named alternative for related color-compositing tasks. The agent is told what the tool does but not under which circumstances it should be chosen.

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.