Get component source
get_component_sourceThe CSS for the component and, if it has behaviour, its part of mian.js.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| part | No |
MIAN
by ro.mian
Schema Changelog
Changes observed during successful MCP inspections.
Changed1 schema field changed
- changed
Input schema / properties / id / enumPrevious value: -[ - "button", - "button-group", - "toggle-group", - "dropdown", - "copy-button", - "swap", - "field", - "input", - "textarea", - "select", - "checkbox", - "radio", - "switch", - "slider", - "file-input", - "input-group", - "number-input", - "otp-input", - "rating", - "combobox", - "calendar", - "tag-input", - "password-input", - "swatch-picker", - "time-slots", - "seat-map", - "radio-card", - "date-range", - "typography", - "avatar", - "badge", - "chip", - "card", - "table", - "list", - "kbd", - "code", - "stat", - "chart", - "timeline", - "accordion", - "description-list", - "divider", - "skeleton", - "empty-state", - "indicator", - "chat", - "tree", - "kanban", - "usage-meter", - "notifications", - "invoice", - "funnel", - "leaderboard", - "product-gallery", - "review-summary", - "post", - "profile-header", - "comment-thread", - "filter-bar", - "bulk-actions", - "curriculum", - "listing-card", - "kpi", - "heatmap", - "gauge", - "breakdown", - "uptime", - "alert", - "toast", - "progress", - "radial-progress", - "spinner", - "banner", - "onboarding", - "loader", - "cookie-consent", - "modal", - "drawer", - "popover", - "tooltip", - "command", - "hover-card", - "context-menu", - "navbar", - "tabs", - "breadcrumbs", - "pagination", - "steps", - "sidebar", - "dock", - "stories-bar", - "page-header", - "collapse", - "carousel", - "theme-controller", - "scroll-area", - "mockup", - "dashboard", - "gradient", - "motion", - "slides", - "jobs", - "work-grid", - "comparison", - "changelog", - "integrations", - "contact-section", - "layout", - "site-header", - "hero", - "logo-cloud", - "feature-grid", - "bento", - "media", - "testimonial", - "pricing", - "cta", - "site-footer", - "article", - "app-shell", - "docs-layout", - "auth", - "price-list", - "team", - "product-card", - "story-card", - "agenda", - "faq", - "figures", - "process" -]New value: +[ + "button", + "button-group", + "toggle-group", + "dropdown", + "copy-button", + "swap", + "hold-button", + "field", + "input", + "textarea", + "select", + "checkbox", + "radio", + "switch", + "slider", + "file-input", + "input-group", + "number-input", + "otp-input", + "rating", + "combobox", + "calendar", + "tag-input", + "password-input", + "swatch-picker", + "time-slots", + "seat-map", + "radio-card", + "date-range", + "task-list", + "duration-picker", + "typography", + "avatar", + "badge", + "chip", + "card", + "table", + "list", + "kbd", + "code", + "stat", + "chart", + "timeline", + "accordion", + "description-list", + "divider", + "skeleton", + "empty-state", + "indicator", + "chat", + "tree", + "kanban", + "usage-meter", + "notifications", + "invoice", + "funnel", + "leaderboard", + "product-gallery", + "review-summary", + "post", + "profile-header", + "comment-thread", + "filter-bar", + "bulk-actions", + "curriculum", + "listing-card", + "kpi", + "heatmap", + "gauge", + "breakdown", + "uptime", + "voice-note", + "alert", + "toast", + "progress", + "radial-progress", + "spinner", + "banner", + "onboarding", + "loader", + "cookie-consent", + "modal", + "drawer", + "popover", + "tooltip", + "command", + "hover-card", + "context-menu", + "navbar", + "tabs", + "breadcrumbs", + "pagination", + "steps", + "sidebar", + "dock", + "stories-bar", + "page-header", + "collapse", + "carousel", + "theme-controller", + "scroll-area", + "mockup", + "dashboard", + "gradient", + "motion", + "slides", + "jobs", + "work-grid", + "comparison", + "changelog", + "integrations", + "contact-section", + "layout", + "site-header", + "hero", + "logo-cloud", + "feature-grid", + "bento", + "media", + "testimonial", + "pricing", + "cta", + "site-footer", + "article", + "app-shell", + "docs-layout", + "auth", + "price-list", + "team", + "product-card", + "story-card", + "agenda", + "faq", + "figures", + "process" +]
Changed1 schema field changed
- changed
Input schema / properties / id / enumPrevious value: -[ - "button", - "button-group", - "toggle-group", - "dropdown", - "copy-button", - "swap", - "field", - "input", - "textarea", - "select", - "checkbox", - "radio", - "switch", - "slider", - "file-input", - "input-group", - "number-input", - "otp-input", - "rating", - "combobox", - "calendar", - "tag-input", - "password-input", - "swatch-picker", - "time-slots", - "seat-map", - "radio-card", - "typography", - "avatar", - "badge", - "chip", - "card", - "table", - "list", - "kbd", - "code", - "stat", - "chart", - "timeline", - "accordion", - "description-list", - "divider", - "skeleton", - "empty-state", - "indicator", - "chat", - "tree", - "kanban", - "usage-meter", - "notifications", - "invoice", - "funnel", - "leaderboard", - "product-gallery", - "review-summary", - "post", - "profile-header", - "comment-thread", - "filter-bar", - "bulk-actions", - "curriculum", - "listing-card", - "alert", - "toast", - "progress", - "radial-progress", - "spinner", - "banner", - "onboarding", - "loader", - "cookie-consent", - "modal", - "drawer", - "popover", - "tooltip", - "command", - "hover-card", - "context-menu", - "navbar", - "tabs", - "breadcrumbs", - "pagination", - "steps", - "sidebar", - "dock", - "stories-bar", - "collapse", - "carousel", - "theme-controller", - "scroll-area", - "mockup", - "slides", - "jobs", - "work-grid", - "comparison", - "changelog", - "integrations", - "contact-section", - "layout", - "site-header", - "hero", - "logo-cloud", - "feature-grid", - "bento", - "media", - "testimonial", - "pricing", - "cta", - "site-footer", - "article", - "app-shell", - "docs-layout", - "auth", - "price-list", - "team", - "product-card", - "story-card", - "agenda", - "faq", - "figures", - "process" -]New value: +[ + "button", + "button-group", + "toggle-group", + "dropdown", + "copy-button", + "swap", + "field", + "input", + "textarea", + "select", + "checkbox", + "radio", + "switch", + "slider", + "file-input", + "input-group", + "number-input", + "otp-input", + "rating", + "combobox", + "calendar", + "tag-input", + "password-input", + "swatch-picker", + "time-slots", + "seat-map", + "radio-card", + "date-range", + "typography", + "avatar", + "badge", + "chip", + "card", + "table", + "list", + "kbd", + "code", + "stat", + "chart", + "timeline", + "accordion", + "description-list", + "divider", + "skeleton", + "empty-state", + "indicator", + "chat", + "tree", + "kanban", + "usage-meter", + "notifications", + "invoice", + "funnel", + "leaderboard", + "product-gallery", + "review-summary", + "post", + "profile-header", + "comment-thread", + "filter-bar", + "bulk-actions", + "curriculum", + "listing-card", + "kpi", + "heatmap", + "gauge", + "breakdown", + "uptime", + "alert", + "toast", + "progress", + "radial-progress", + "spinner", + "banner", + "onboarding", + "loader", + "cookie-consent", + "modal", + "drawer", + "popover", + "tooltip", + "command", + "hover-card", + "context-menu", + "navbar", + "tabs", + "breadcrumbs", + "pagination", + "steps", + "sidebar", + "dock", + "stories-bar", + "page-header", + "collapse", + "carousel", + "theme-controller", + "scroll-area", + "mockup", + "dashboard", + "gradient", + "motion", + "slides", + "jobs", + "work-grid", + "comparison", + "changelog", + "integrations", + "contact-section", + "layout", + "site-header", + "hero", + "logo-cloud", + "feature-grid", + "bento", + "media", + "testimonial", + "pricing", + "cta", + "site-footer", + "article", + "app-shell", + "docs-layout", + "auth", + "price-list", + "team", + "product-card", + "story-card", + "agenda", + "faq", + "figures", + "process" +]
- First observed
TDQS
C2.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact — JS is only returned 'if it has behaviour' — which tells the agent output shape varies by component. It says nothing about permissions, error behavior, or whether the code is raw or transformed, so the disclosure is partial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with no filler, which is good, but it is under-specified rather than concise, and it contains a typo ('mian.js') that could confuse an agent looking for a real filename. The conditional clause is awkwardly placed after the main assertion.
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?
A two-parameter tool with no annotations, no output schema, and 0% schema coverage should explain its return shape and the role of each parameter. The description covers only one of the two parameters and omits any statement of what the response actually looks like (file contents, code blocks, concatenated output).
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?
Schema description coverage is 0%, so the description must compensate for both parameters. It never mentions the 'part' parameter (enum css/js/both) at all, even though its wording implies a fixed combined response — leaving the agent to discover the selector from the schema alone. The 'id' parameter's meaning is only implied by the phrase 'the component'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description names the resource ('the CSS for the component') and the conditional JS payload, so an agent can infer this retrieves source code for a component. However, it never states the verb (get/retrieve) and gives no differentiation from close siblings like get_noodle_css, get_component, or get_noodle, leaving ambiguity about which fetch tool to pick.
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?
There is no statement of when to use this tool versus alternatives, and the sibling list contains several overlapping retrieval tools (get_component, get_noodle_css, get_example). No prerequisites, no exclusion conditions, no routing guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.