Skip to main content
Glama
@vaneui/mcp

@vaneui/mcp

Official
by vaneui

get_component_props

Returns boolean props for a VaneUI component by slug, with defaults marked and shared layout categories listed; use detail full for descriptions and all shared props.

Instructions

Return a VaneUI component's boolean props, one line per category, default marked *. By default (compact) it lists the component's own props and names the shared layout categories it takes; slug common lists those once. detail full adds descriptions and every shared prop. Value props such as label or title are on the component's page: call get_doc with the same slug. The slug is the resource basename: button, card, icon-button, etc.

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": {
      "slug": "<slug>"
    },
    "name": "get_component_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesComponent slug, or `common` for the shared layout props. A component name (`IconButton`) works too.
detailNo`compact` (default) or `full`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the output formatting convention (one line per category, `*` for defaults), what `compact` versus `full` returns, and how `common` collapses shared categories. It stops short of stating that the operation is purely read-only or what happens for an unknown slug.

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?

Front-loaded with purpose and output format, then defaults, then the get_doc pointer, then slug conventions — a sensible order. It is dense and slightly run-on in the middle sentences, but nearly every clause carries information.

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 two-parameter read lookup with no output schema and no annotations, the description covers return format, default mode, escalation mode, the special `common` slug, and the hand-off to get_doc. Only edge behavior (invalid slug, component with no boolean props) is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it defines the slug as "the resource basename" with concrete examples (`button`, `card`, `icon-button`) and spells out what `detail: full` actually adds (descriptions plus every shared prop), which the schema does not.

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?

States a specific verb and resource ("Return a VaneUI component's boolean props") and immediately describes the output shape ("one line per category, default marked `*`"). It also draws the boundary against the sibling tool by naming get_doc as the place for value props like `label` or `title`.

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

Usage Guidelines5/5

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

Explicitly explains the default behavior (`compact`), the `common` slug case for shared layout categories, and the `full` detail escalation, plus a clear routing rule to get_doc for value props. There is little left to infer about when this tool is the right choice.

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