Skip to main content
Glama

fill_gradient

Fill a rectangular area with a density gradient along a chosen direction to create skies, fog, fades, and atmospheric depth in ASCII art without using an image.

Instructions

Fill a rectangular region with a density gradient (empty to full along a direction). Ideal for skies, fog, fades, and atmospheric depth without needing an image.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "fill_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
rampNoDensity ramp from empty to full. .:-=+*#%@
widthYes
heightYes
directionNodown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden: it discloses that the operation paints into a bounded region and follows a direction, which implies overwrite of existing content in that area. It does not confirm that implication, nor does it say whether an existing canvas is required, what happens at region edges, or what the size limits are.

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?

Two sentences, zero filler: the mechanic comes first, the motivating use cases second. Nothing is repeated from the schema and nothing could be cut without losing information.

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?

For a 6-parameter mutation tool with no annotations, no output schema, and near-zero schema descriptions, the definition covers the concept and the 'why' well. It leaves meaningful gaps around the radial direction mode, the 400x400 limits, and the overwrite behavior an agent needs to call it safely.

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 only 17%, so the description must compensate. It usefully clarifies the ramp as 'empty to full' (better than the schema's 'Density ramp from empty to full'), but it never mentions the 'radial' option in the direction enum, saying only 'along a direction', and says nothing about x/y/width/height limits or semantics.

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 names a specific verb and resource — 'Fill a rectangular region with a density gradient' — plus the defining trait (empty to full along a direction). The phrase 'without needing an image' implicitly distinguishes it from image_to_ascii and draw_rect, so an agent can pick it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete use cases — skies, fog, fades, atmospheric depth — which tell the agent when this tool is the right choice. It stops short of stating exclusions or naming a sibling to use instead for solid fills or patterned fills, so it is clear context rather than full routing guidance.

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