Skip to main content
Glama

design_audit

Read-onlyIdempotent

Performs a read-only scan of project files to detect potential UI consistency issues without modifying any files.

Instructions

Read-only scan for potential UI consistency issues; does not alter project files.

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": {
      "project_path": "<project_path>"
    },
    "name": "design_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so 'read-only' and 'does not alter project files' are essentially restatements of the structured metadata. The only added nuance is the word 'potential,' hinting at heuristic findings, but nothing is said about what gets scanned, what counts as an issue, or how results are surfaced.

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?

A single tight clause with the read-only guarantee front-loaded and no filler. It is efficient, though its brevity is partly the cause of the gaps in other dimensions.

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

Completeness2/5

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

There is no output schema, no parameter documentation, and no explanation of what a scan result contains, so an agent cannot anticipate the report shape or scope of the audit. For a tool that presumably produces a findings list, that is a meaningful omission.

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% and the description says nothing about project_path. With one required parameter it is unclear whether it expects a directory root, a specific file, or whether the path is relative to a workspace; neither the schema nor the description resolves that.

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?

States a specific verb and resource: a 'read-only scan for potential UI consistency issues.' That is enough for an agent to know it audits design/UI consistency rather than accessibility (browser_axe_audit) or design-library lookup, but it never explicitly contrasts itself with those siblings, so the boundary has to be inferred from naming.

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 or when-not-to-use guidance, no prerequisites, and no named alternative. An agent knows only that the tool is safe to call, not what situation should trigger it versus browser_axe_audit or design_read.

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