UX Pilot

import

Bring something into UX Pilot. kind: html (your HTML as a new screen, free unless refine; Tailwind classes, gap and padding, not margins: guide topic html), url (a live page, credits), assets (images by URL), upload (base64 images), design_system (code, a repository, a site or tokens).

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

Input Schema

Name	Required	Description
`kind`	No	What to import.
`params`	No	The action's fields. guide({ topic: "<tool>.<action>" }) lists them.
`confirmed`	No	true only after the user agreed to this call.
`confirmationToken`	No	The token the first call answered with.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the simple boolean annotations, the description adds crucial behavioral constraints. For instance, it warns that HTML imports are 'free unless refine' and specifies required styling conventions like using Tailwind classes and avoiding margins.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single, dense sentence which makes it difficult for an AI to parse quickly. While it contains all necessary information, it lacks clear structure, making it less digestible than a bulleted list would be.

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?

The description is highly complete given the tool's complexity and the dynamic nature of the 'params'. It provides enough information for an agent to properly construct a request and understand the limitations of the imported content types.

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

Parameters5/5

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

Since the schema coverage is 100%, the description is highly valuable. It adds semantic depth by detailing specific input requirements for each kind, such as listing acceptable formats for design systems (code, repository, site, tokens).

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 purpose is clearly stated as bringing content into UX Pilot. The description specifies the different 'kinds' of content that can be imported, making the tool's domain clear to the agent.

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?

The description offers no guidance on when this tool should be used versus alternatives. It is an all-encompassing import tool, and the lack of context regarding when to choose 'url' vs 'assets' provides no helpful differentiation.

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

All UX Pilot tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.