Skip to main content
Glama

Generate Form Styles

generate_form_styles

Generates accessible form CSS from a single brand color, covering labels, inputs, placeholders, hover, focus, error, disabled states, and help text while verifying contrast.

Instructions

Accessible form CSS from one brand color: labels, inputs, placeholders, hover, focus-visible, error and disabled states, help and error text, and checkbox/radio accents, with every contrast requirement verified. Deterministic, no API key needed.

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": {
      "brand": "<brand>"
    },
    "name": "generate_form_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand color as hex
errorNoError color as hex#dc2626

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses deterministic output, no API key requirement, comprehensive state coverage, and verified contrast. It does not specify the exact return format (e.g., CSS string vs. file), leaving a small gap.

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 front-loaded and efficient: it opens with the core output and input, then lists the covered states in a compact clause, followed by two short behavioral notes. No sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generator with no output schema and two parameters, the description covers scope, included states, contrast verification, determinism, and lack of an API key. It is nearly complete, though it could clarify the return type more explicitly.

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% and both parameters have descriptions, so the schema already does the heavy lifting. The description reinforces the required 'brand' input as 'one brand color' but adds no detail about the optional 'error' parameter or its default.

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 states it produces accessible form CSS from a brand color and enumerates the covered form elements and states. It does not explicitly contrast itself with sibling tools like generate_component_states, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the form-specific scope and the 'no API key needed' note, but there is no explicit when-to-use or when-not-to-use guidance relative to alternatives.

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