Skip to main content
Glama

Get AI-UI Design System

get_ai_ui
Read-only

Overview of the AI-UI design system (20 accessible Astro components for AI reasoning, execution pipelines, and streaming chat), package install instructions, and pointer to the dedicated sub-MCP server at https://www.michaelvereb.com/ai-ui/mcp.

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_ai_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safe read-only, closed-world, non-destructive profile, so the bar is lower. The description adds real context beyond them: it names the payload contents and, importantly, discloses that a separate sub-MCP server exists for deeper access—information the agent could not get from structured fields.

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?

One sentence, front-loaded with the resource, then the enumerated contents and the external pointer. Dense and free of filler, though the nested parenthetical and URL make it slightly harder to scan than a short bulleted statement.

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 zero-parameter read-only overview with no output schema, the description is close to sufficient. It never clarifies whether the returned pointer means the agent must subsequently call the sub-MCP server, which leaves a real gap in how to act on the result.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case; there is nothing to disambiguate. The description correctly implies no inputs are needed by framing the call as a fetch of an overview.

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?

States a specific resource (the AI-UI design system) and enumerates exactly what the call returns: an overview of 20 Astro components, package install instructions, and a pointer to the sub-MCP server. No sibling covers this resource, so the agent can route here without ambiguity.

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?

Usage is only implied—read this when you need to orient to the AI-UI system. There is no explicit when-to-use/when-not guidance, and no statement about whether to call this before or instead of querying the sub-MCP server it points to.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources