Skip to main content
Glama
Sign In
gluestack-ui-mcp-server

gluestack-ui-mcp-server

by gauravsaini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_component

Retrieve the source code for any Gluestack UI component by name. Specify a variant like nativewind or themed to get the exact code you need.

Instructions

Get the source code for a specific Gluestack UI component

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

Input Schema

NameRequiredDescriptionDefault
componentNameYesName of the Gluestack UI component (e.g., 'Button', 'Input', 'Modal')
variantNoComponent variant to retrieve (defaults to nativewind if available)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

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 carry the full burden. It only states a read operation ('Get') but does not confirm non-destructive nature or mention any side effects, authentication, or limits. Minimal disclosure.

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?

Single sentence, front-loaded, no unnecessary words. Efficient and to the point.

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?

No output schema and only one sentence. Does not describe the return format (e.g., string of source code). Suitable for a simple tool but lacks clarity on what the agent will receive.

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%, so the description adds no extra meaning beyond what the schema already provides for componentName and variant. Baseline 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?

The description clearly states the tool retrieves the source code for a specific Gluestack UI component. It distinguishes from sibling tools like get_component_demo or get_component_metadata by specifying 'source code'.

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 guidance on when to use this tool versus alternatives. With siblings like get_component_demo and get_component_metadata, the description should indicate scenarios for each but does not.

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

Deploy Server

Other Tools