gluestack-ui-mcp-server

get_component_demo

Retrieve demo code illustrating proper usage of any Gluestack UI component, with variant options for nativewind, themed, or unstyled.

Instructions

Get demo code illustrating how a Gluestack UI component should be used

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": {
      "componentName": "<componentName>"
    },
    "name": "get_component_demo"
  }
}

Input Schema

Name	Required	Description	Default
`componentName`	Yes	Name of the Gluestack UI component (e.g., 'Button', 'Input', 'Modal')
`variant`	No	Component variant to retrieve demo for (defaults to nativewind)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Jun 17, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, and the description lacks detail on what exactly is returned (e.g., code snippet, file path), side effects, or authorization needs. It only says 'Get demo code', which is insufficient for transparency.

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?

Description is a single sentence with no filler, front-loading the purpose. However, it is slightly too concise given the lack of behavioral details.

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 tool with two well-described parameters and no output schema, the description gives the minimum viable context. It could mention the return format or constraints (e.g., componentName must exist).

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?

The input schema already has 100% description coverage for both parameters, including the default for 'variant'. The description adds no new semantic meaning beyond what is in 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?

Description clearly states the tool retrieves demo code for a Gluestack UI component, specifying the resource (demo code) and purpose (illustrating usage). It distinguishes from siblings like 'get_component' which likely gets the component itself.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_component_metadata' or 'list_component_variants'. The usage context is implied but not stated.

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

Deploy Server