Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

audit_design

Read-onlyIdempotent

Inspect HTML, CSS and copy to flag actionable design issues, returning evidence, fixes and scope so coding agents know what to revise.

Instructions

Inspect supplied HTML, CSS and copy for actionable issues. Returns evidence, fixes and scope.

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": "audit_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
cssNo
copyNo
htmlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds that the caller gets back evidence, fixes and scope — useful output context since there is no output schema — but says nothing about the analysis depth, how findings are ranked, or what 'scope' means.

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?

Two sentences, front-loaded with the action, no filler. The second sentence is terse to the point of vagueness, but the size is well matched to a simple analysis tool.

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 read-only tool with three optional string inputs, an agent still needs to know which inputs are required to get useful results and what the returned evidence/fixes/scope look like, since there is no output schema. The description gestures at these but leaves the minimum-input question and return structure unresolved.

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

Parameters2/5

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

Schema description coverage is 0% with three free-form string parameters, so the description must add meaning, but it only echoes the parameter names already present in the schema. It does not say what form the HTML/CSS/copy should take, whether all three are expected, or what happens when nothing is supplied (all parameters are optional).

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 verb 'Inspect' and the resources 'HTML, CSS and copy' are specific, and 'actionable issues' frames the intent. It does not name any sibling or state how it differs from the design-pack, inspiration, or icon tools, which is the only thing keeping it from 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no exclusions or alternatives. An agent must infer from the tool name alone that it should use this when it has authored markup rather than when it wants to retrieve existing design assets.

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