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

gluestack-ui-mcp-server

by gauravsaini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_directory_structure

Retrieve the directory structure of the Gluestack UI repository. Specify a path and depth to navigate components and files for development.

Instructions

Get the directory structure of the Gluestack UI repository or a specific path within it

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath within the Gluestack UI repository (relative to root). Leave empty for full structure.
depthNoMaximum depth to traverse (default: 3)
includeFilesNoWhether to include files in the structure (default: true)

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 provided; the description does not mention error handling, auth requirements, or response format. It only states the basic function without behavioral details.

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?

Single sentence that is front-loaded with purpose. Efficient but could be slightly more structured with separate usage notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 3 optional parameters and no output schema, the description is minimal. It lacks details on depth behavior, file inclusion semantics, and error cases, making it incomplete for confident use.

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 covers all 3 parameters with descriptions. The tool description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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 it retrieves the directory structure of the Gluestack UI repository, optionally filtered by path. This distinguishes it from sibling tools which deal with components and variants.

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 or not, but the context from sibling tool names implies it is for exploring file structure rather than components.

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