Hi-AI

preview_ui_ascii

Read-onlyIdempotent

Generate ASCII art previews of UI layouts and components to visualize page designs before writing code.

Instructions

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": {
      "page_name": "<page_name>",
      "components": "<components>"
    },
    "name": "preview_ui_ascii"
  }
}

Input Schema

Name	Required	Description
`page_name`	Yes	Name of the page or component (e.g., "Login Page", "Dashboard")
`layout_type`	No	Layout structure type (default: header-footer)
`components`	Yes	List of UI components to include
`width`	No	Preview width in characters (default: 60)
`responsive`	No	Show mobile view preview (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jan 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already provide clear behavioral hints (readOnlyHint: true, destructiveHint: false, idempotentHint: true). The description adds valuable context by specifying that this is a 'preview' tool for UI design before actual coding, which clarifies its non-destructive, planning-oriented nature. This goes beyond what annotations provide by explaining the tool's role in the development workflow.

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?

The description is efficiently structured with a list of synonymous action verbs followed by the core purpose 'Preview UI before coding.' It's front-loaded with key terms and avoids unnecessary elaboration. The only minor inefficiency is the repetitive list of verbs, but overall it's appropriately concise for the tool's complexity.

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?

Given the rich annotations (readOnly, non-destructive, idempotent) and 100% schema coverage, the description provides adequate context for this preview tool. The description clarifies the tool's role in the UI design workflow, which complements the structured data. The main gap is the lack of output schema, but the description doesn't need to explain return values since it's a preview tool.

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 description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description doesn't add any additional parameter semantics beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete, but doesn't provide extra value.

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's purpose: 'Preview UI before coding' with multiple synonymous verbs (create, build, design, make, develop). It specifies the resource (UI/page/component) and the action (preview). However, it doesn't explicitly differentiate from sibling tools, which appear to be analysis/memory/planning tools rather than UI preview tools, so the distinction is implicit rather than explicit.

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 implies usage context through the phrase 'Preview UI before coding,' suggesting this is for design/planning phases. However, it doesn't provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The sibling tools are mostly analysis/memory tools, so the distinction is clear but not explicitly stated.

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