Skip to main content
Glama
Sign In
Ant Design MCP Server

Ant Design MCP Server

by leonwgc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_components_by_category

Retrieve all Ant Design components by category, such as Layout or Data Entry, to find relevant components for your UI.

Instructions

Get all components in a specific category (General, Layout, Navigation, Data Entry, Data Display, Feedback, Other).

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": {
      "category": "<category>"
    },
    "name": "get_components_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesComponent category (General, Layout, Navigation, Data Entry, Data Display, Feedback, Other)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. It omits whether it returns full component objects or just names, any pagination behavior, or auth requirements. For a tool with zero annotation coverage, this is a significant gap.

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?

The description is a single sentence that conveys all necessary information without any wasted words. It is front-loaded and efficient.

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

Completeness3/5

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

Given the simplicity of the tool (one parameter, no output schema), the description is mostly adequate but lacks mention of the return format (e.g., names, full component data). The list of categories aids use but does not fully compensate for the missing output details.

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%, and the tool description adds no new semantics beyond the schema. The parameter description is effectively identical. Baseline score of 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 action ('get all components') and the filter ('in a specific category'), with explicit list of valid categories. This distinguishes it from siblings like get_all_component_names (no filter) and search_components (search-based).

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 you need components by category, but does not explicitly contrast with alternatives (e.g., 'use get_all_component_names for unfiltered list'). The lack of explicit when-not or alternative guidance prevents a higher score.

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