Skip to main content
Glama

Generate Shadow Scale

generate_shadows

Generate layered elevation shadows from xs to 2xl in soft or crisp styles, tinted to a base color, as CSS or JSON for consistent UI depth.

Instructions

Layered elevation shadows (xs to 2xl) in a soft or crisp style, tinted to a base color. Deterministic, no API key needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_shadows"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoShadow tint as hex#0f172a
styleNosoft
formatNocss
levelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output is deterministic and requires no API key, but it omits return format details, what the levels map to, and whether the CSS/JSON output differs structurally.

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?

The description is a single front-loaded sentence with no wasted wording. Purpose, style range, tinting, and key guarantees are packed efficiently.

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 simple generator this is minimally adequate, but with no output schema and no annotations the description should say more about the returned structure and the format parameter. It covers the core purpose but leaves meaningful gaps for an agent invoking it.

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 25%, so the description needs to compensate. It adds meaning for style (soft/crisp) and color tinting and implies the level scale runs xs to 2xl, but it does not explain the format parameter (css vs json) or how the integer levels parameter maps to those named sizes.

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 clearly identifies the resource: layered elevation shadows from xs to 2xl, with soft or crisp styling and base-color tinting. It does not explicitly state a verb or name sibling alternatives, but the shadow-specific output is distinct from the other design-token generators.

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 guidance on when to use this tool versus alternatives such as generate_design_system or generate_component_states. It implies its use through the output description but includes no context, exclusions, or routing guidance.

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