Skip to main content
Glama
Sign In
uxloom

uxloom

Official
by uxloom-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

screen_critique

Validate a single UI screen for usability, accessibility, and state coverage gaps. Submit a screen ID to get findings that support iterative design improvements.

Instructions

Findings scoped to a single screen. Use during iteration on one screen.

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": {
      "screenId": "<screenId>"
    },
    "name": "screen_critique"
  }
}

Input Schema

NameRequiredDescriptionDefault
screenIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool is scoped to a screen but does not mention whether it is read-only, what happens on invalid screenId, or any limits. This is insufficient.

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 extremely concise with two short sentences, front-loading the key purpose. No unnecessary words.

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 simple single-parameter tool with no output schema, the description provides minimal but adequate context for basic usage. However, it omits details like return format and error behavior, leaving gaps for an AI agent.

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

Parameters1/5

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

The single parameter screenId has 0% schema description coverage, and the description adds no semantics about it (e.g., format, how to obtain, default behavior). The description does not compensate for the missing schema documentation.

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 the tool returns findings scoped to a single screen, distinguishing it from broader siblings like coverage_report or project_audit. The verb 'scoped' is slightly passive but sufficient.

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?

The description advises using during iteration on one screen, implying when to use but does not explicitly state when not to use or mention alternatives. The sibling tool list provides context but is not referenced.

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

Deploy Server

Other Tools