Skip to main content
Glama

Feature Library

Check a build’s touch on a look

check_look
Read-only

Free. Runs the library’s own checker on how a build uses a look: each override is one of the look’s knobs, of its kind and in range; each switch is one of its options; and text contrast holds (WCAG AA) in each mode at the dials’ extremes with the overrides applied. Returns ok, the problems in sentences, the label the build may use ("In Splash", "Splash, tuned"; none for inspired) and, for a tuned build that passes, the stylesheet to load after the look’s.

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": {
      "look": "<look>"
    },
    "name": "check_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookYesThe look id, e.g. splash.
modeNoOptional: check one mode; every mode the look has when left out.
dialsNoOptional: { liveliness, fidelity, density }, each 0 to 100; the look’s own for any left out.
levelNoOptional: tuned when overrides are given, otherwise exact.
switchesNoOptional: switch values by attribute, e.g. { "data-splash-drips": "liquid" }.
overridesNoOptional: knob values, { "--accent": "#0f6e66" } for every mode, or per mode { "light": {…}, "dark": {…} }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the tool is free, what the library's checker validates, the WCAG AA contrast condition, and the exact return values including the label and stylesheet behavior. This is rich behavioral context with no contradiction.

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 with the cost and core action, then moves through validation rules and return values without wasted wording. The long middle sentence is dense but every clause carries relevant information.

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

Completeness5/5

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

For a six-parameter tool with nested objects and no output schema, the description is complete: it explains the validation model and describes the return payload, including labels and conditional stylesheet output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining that overrides must match the look's knobs and ranges, switches must match its options, and dials affect contrast at extremes. It does not fully restate every parameter, which keeps it from a 5.

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 states a specific verb and resource: it runs the library's checker on how a build uses a look, and it enumerates the validation dimensions. It is clear what the tool does, but it does not explicitly distinguish this from the sibling check tool.

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 context for what is checked and notes that the tool is free, but it does not say when to use this tool versus alternatives such as check. It also gives no explicit exclusions or prerequisites.

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.

Resources