Skip to main content
Glama
Sign In
zygiu-zygis

basecoat-ui

by zygiu-zygis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_component_details

Read-onlyIdempotent

Retrieve a Basecoat component's minimal template, dependencies, and composition tips for Astro, HTML, React, Vue, or Svelte. Call with no ID to get the component catalog index.

Instructions

Get one minimal component template, dependencies, and composition tips for Astro or HTML. Valid IDs: any of the 57 Basecoat components (button, card, dialog, dropdown-menu, table, tabs, badge, etc.). When called with {}, returns the top-level component catalog index. Next step: Call validate_composition or basecoat_quality_inspector after integrating markup.

Input Schema

NameRequiredDescriptionDefault
idNoBasecoat component ID from search_components (e.g., "button", "dialog", "card", "dropdown-menu", "table", "tabs").
nameNoAlternative component identifier alias.
componentIdNoAlternative component identifier alias.
environmentNoTarget framework/environment template to output (defaults to "html").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.8.0
    • addedInput schema / properties / componentId
      Added value: +{
+  "description": "Alternative component identifier alias.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / environment / description
      Added value: +"Target framework/environment template to output (defaults to \"html\")."
    • changedInput schema / properties / environment / enum
      Previous value: -[
-  "astro",
-  "html"
-]New value: +[
+  "html",
+  "astro",
+  "react",
+  "vue",
+  "svelte"
+]
    • addedInput schema / properties / id / description
      Added value: +"Basecoat component ID from search_components (e.g., \"button\", \"dialog\", \"card\", \"dropdown-menu\", \"table\", \"tabs\")."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alternative component identifier alias.",
+  "maxLength": 80,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id",
-  "environment"
-]
  2. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/false openWorld, so the safety profile is covered. The description still adds genuine behavioral context: the special empty-argument mode returning a catalog index, and the intended workflow position after integration.

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?

Three sentences, front-loaded with purpose, then valid IDs, then the empty-call behavior and next step. Efficient, though the 'Astro or HTML' qualifier adds a slightly misleading constraint that costs a point.

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

Completeness4/5

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

For a read-only, no-required-parameter tool with no output schema, the description covers what is returned, the empty-argument edge case, and the follow-on tools. It is close to complete; only the relationship to get_component_html and the framework coverage discrepancy are unaddressed.

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 baseline is 3. The description does add the universe of valid ids (57 Basecoat components) and the {} semantics, but it says templates are 'for Astro or HTML' while the environment enum also offers react, vue and svelte — a mild mismatch that could steer the agent away from valid options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get one minimal component template plus dependencies and composition tips), and the word 'one' scopes it against the list-returning search_components. It never names a sibling explicitly, so the agent must infer the boundary from the ID list rather than being told.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage context: an empty {} call returns the catalog index, and it prescribes the follow-up step (validate_composition or basecoat_quality_inspector after integrating markup). It does not say when to prefer get_component_html or another sibling over this tool, so the alternatives side is missing.

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