Skip to main content
Glama
Sign In
Ant Design MCP Server

Ant Design MCP Server

by leonwgc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_component_example

Retrieves a complete usage example for an Ant Design component, providing TypeScript and React code for integration.

Instructions

Get a complete usage example for a specific Ant Design component with TypeScript and React code.

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_example"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentNameYesThe name of the Ant Design component

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must detail behavioral traits. It only says 'complete usage example' without specifics on what completeness means (e.g., includes imports, full code, or just a snippet), nor any constraints or additional behavior.

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?

The description is a single sentence that is concise and front-loaded. It gets the point across without waste, but could be slightly more informative without losing conciseness.

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 simple tool with one parameter and no output schema, the description covers the basic purpose and output. It mentions TypeScript and React, adding relevant context. However, it could be more precise about the format of the example.

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 schema already documents the parameter. The description adds no extra meaning beyond 'the name of the Ant Design component', not specifying casing or format. Baseline 3 is appropriate.

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 specific resource 'a complete usage example for a specific Ant Design component with TypeScript and React code', differentiating it from sibling tools like get_component_info which likely returns metadata, not code examples.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives like get_component_info or search_components. Usage is implied from the purpose, but no exclusions or context are provided.

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