Skip to main content
Glama

Get the AI Canvas audit checklist

get_audit_checklist
Read-onlyIdempotent

Returns a final audit checklist for AI Canvas pages or components, covering install, prop validation, themes, 320px layout, motion cleanup, keyboard/contrast, and composition. Use it before sign-off.

Instructions

Return the checklist to run on a finished page or component built with AI Canvas parts: install completeness, prop correctness (via validate_usage), both themes, layout at 320px, motion cleanup and reduced motion, keyboard and contrast, and composition rules. Use it as the last step of a build, or whenever the user asks "is this done right".

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

Input Schema

NameRequiredDescriptionDefault
scopeNo"page" (default) for a composed screen, "component" for a single adapted or hand-built component.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. The description adds genuine value beyond that by disclosing the content and sequence of what comes back (a multi-area audit including motion cleanup and reduced motion, keyboard and contrast). It does not describe the checklist's format or granularity, which keeps it below a 5.

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 return value and followed by the trigger condition. The long itemized list of audit areas is dense but each entry helps an agent confirm the tool covers the check it needs, so little is wasted; a slightly tighter enumeration would earn a 5.

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 one-optional-parameter, read-only tool with no output schema, the description carries the burden of explaining what is returned and does so by enumerating the checklist's coverage. The only minor gap is how results are presented (checklist items vs. pass/fail guidance), which an agent might want before invoking.

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 the enum values 'page'/'component' are already documented in the schema, so the baseline is 3. The description's phrase 'a finished page or component' loosely echoes those two scopes but adds no new syntax, defaults, or usage nuance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Return the checklist to run on a finished page or component built with AI Canvas parts') and then enumerates the exact audit areas covered (install completeness, prop correctness, themes, 320px layout, motion, keyboard/contrast, composition). This clearly distinguishes it from sibling lookup tools like validate_usage or get_component, which return data rather than an audit procedure.

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

Usage Guidelines4/5

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

It gives a concrete trigger: 'Use it as the last step of a build, or whenever the user asks "is this done right".' That tells the agent both a lifecycle position and a user-intent signal. It stops short of explicit when-not/exclusion guidance, though naming validate_usage as a sub-step inside the checklist implicitly routes prop checking elsewhere.

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