Skip to main content
Glama
Sign In
Ant Design MCP Server

Ant Design MCP Server

by leonwgc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_component_info

Retrieve detailed information about an Ant Design component, including its props, usage examples, and API documentation.

Instructions

Get detailed information about a specific Ant Design component including description, props, usage examples, and API documentation URL.

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": {
      "componentName": "<componentName>"
    },
    "name": "get_component_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentNameYesThe name of the Ant Design component (e.g., "Button", "Form", "Table")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the returned information categories (description, props, etc.), but does not mention if the tool performs network requests, requires authentication, or has any side effects. Adequate but not exhaustive.

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 conveying all essential information without redundancy. No unnecessary words; every phrase is functional.

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?

Given the tool's simplicity (1 parameter, no output schema), the description covers the core purpose and return content. Minor omission: does not explicitly state that the tool is read-only or mention error behavior, but overall sufficient.

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 coverage is 100% (componentName with description and example). The description adds no additional semantic meaning beyond what the schema already provides. Baseline score 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 explicitly states the tool's purpose: retrieving detailed component information (description, props, usage examples, API URL). This clearly distinguishes it from sibling tools like get_all_component_names or get_component_example.

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?

The description implies usage when a specific component name is known, but does not explicitly state when to avoid it (e.g., for listing all components) or note alternatives. However, sibling context provides implicit guidance.

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