Skip to main content
Glama

TinyFn

desaturate_color

Decrease color saturation by a percentage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoAmount to desaturate (0-100)
hex_colorYesHex color to desaturate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
darkenedNo
originalYes
lightenedNo
saturatedNo
desaturatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic operation. It does not disclose any behavioral traits such as whether it modifies the original color or what happens at extreme values, nor does it mention that an output schema is provided.

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?

Very concise single sentence with no wasted words; front-loaded but slightly under-specified given the two parameters.

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 description is basic but sufficient for a simple color manipulation tool. However, it omits mention of the output format (hex color) and does not explain edge cases like amount=0 or 100.

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 coverage is 100%, so baseline 3. The description mentions 'by a percentage' which partially aligns with the amount parameter but adds no new detail beyond the schema's min/max/default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Decrease color saturation by a percentage' clearly states the action and resource, distinguishing it from siblings like saturate_color or invert_color.

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?

No guidance on when to use this tool versus alternatives like saturate_color or grayscale_color; no mention of prerequisites or context.

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.