get_component
Get a component's full Blade source, dependencies, required packages and install command.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
blatui
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description lists returned items but does not disclose potential side effects, authentication needs, or rate limits. Adequate but could be more transparent.
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, 12 words, front-loaded with key information. No unnecessary detail.
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 one parameter and no output schema, the description adequately states what is returned but lacks usage context and parameter detail. Minimum viable completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only parameter 'name' has no schema description (0% coverage) and the description does not elaborate on its meaning or expected format. Does not add value beyond 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?
The description clearly states the verb 'Get' and the resource 'a component's full Blade source, dependencies, required packages and install command', distinguishing it from siblings like get_example or install_command.
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 like get_example or search_registry. The description lacks context for usage.
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.
TDQS
A3.6/5.0
Disambiguation4/5
Each tool targets a different aspect (component details, block/chart examples, installation commands, listing, searching). There's slight potential confusion between get_component and get_example, as both return source code, but they serve different entities (components vs blocks/charts) as clarified by descriptions.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (get_component, get_example, install_command, list_components, search_registry), making it easy for an agent to predict tool behavior based on the name.
Tool Count5/5
With 5 tools covering listing, searching, detailed retrieval, examples, and installation commands, the count is well-scoped for a registry-focused server without being too sparse or overwhelming.
Completeness5/5
The tool set provides full coverage for browsing and installing BlatUI components: listing, searching, getting details, getting examples, and generating install commands. No obvious gaps for the stated purpose.