gluestack-ui-mcp-server

get_component_metadata

Retrieve props, dependencies, and usage examples for any Gluestack UI component to simplify implementation.

Instructions

Get metadata for a specific Gluestack UI component including props, dependencies, and examples

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Jun 17, 2026

TDQS

B3.3/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 convey behavioral traits. It only states the tool retrieves metadata, but does not disclose whether it is read-only, requires authentication, has rate limits, or any side effects. This is insufficient for a tool with no annotations.

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 a single, well-structured sentence that efficiently conveys the tool's purpose without 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?

Given no output schema and no annotations, the description minimally covers what the tool returns (props, dependencies, examples) but lacks details on output format, error handling, or prerequisites. It is adequate but incomplete.

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 coverage is 100% with clear parameter descriptions for componentName and variant. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 verb 'Get' and resource 'metadata for a specific Gluestack UI component', and specifies what is included (props, dependencies, examples). This distinguishes it from sibling tools like get_component (likely returns component code) and get_component_demo (returns demo).

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?

No explicit guidance on when to use this tool versus alternatives like get_component or list_components. The description does not mention when-not or provide context for selection beyond the tool's purpose.

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

Deploy Server