Skip to main content
Glama

list_all_components

Retrieve all available component names from Korea's government digital design system (KRDS) to browse UI elements for Korean government digital services.

Instructions

모든 KRDS 컴포넌트 이름 목록을 가져옵니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that implements the 'list_all_components' tool logic by loading all KRDS components via the loader and returning a sorted list of component names.
    export async function listComponentNames(loader: KRDSLoader): Promise<string[]> {
      const allComponents = await loader.loadComponents();
      return allComponents.map(c => c.name).sort();
    }
  • src/index.ts:143-150 (registration)
    Tool registration in the getTools() method, defining the tool name, description, and empty input schema.
    {
      name: 'list_all_components',
      description: '모든 KRDS 컴포넌트 이름 목록을 가져옵니다.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Wrapper handler in the MCP server that calls the core listComponentNames function and formats the response as formatted text.
    private async handleListComponents() {
      const components = await listComponentNames(this.loader);
      const text = `KRDS 컴포넌트 목록 (${components.length}개):\n\n${components.map(c => `• ${c}`).join('\n')}`;
      
      return {
        content: [{ type: 'text', text }],
      };
  • Switch case dispatcher that routes calls to the 'list_all_components' tool to its handler method.
    case 'list_all_components':
      return await this.handleListComponents();
  • Input schema definition for the tool, specifying an empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior, or what format the returned list takes. '가져옵니다' (fetches) implies reading data, but no further details are given.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a simple list operation, though it could potentially be more structured if it included usage context.

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?

For a list operation with no annotations and no output schema, the description is insufficient. It doesn't explain what the returned data looks like (e.g., array format, whether it includes metadata), nor does it address behavioral aspects like performance considerations or error conditions. The context signals indicate this is a simple tool, but more completeness is needed.

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?

The tool has zero parameters, and schema description coverage is 100% (empty schema is fully documented). The description appropriately doesn't discuss parameters since none exist. A baseline of 4 is appropriate for zero-parameter tools when the schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('가져옵니다' - 'fetches') and resource ('모든 KRDS 컴포넌트 이름 목록' - 'list of all KRDS component names'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'search_krds_components' or 'list_component_categories', but the 'all' scope provides some implicit distinction.

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?

No guidance is provided about when to use this tool versus alternatives like 'search_krds_components' (which might allow filtering) or 'list_component_categories' (which might organize components differently). The description only states what it does, not when it's appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/re-rank/UIUX-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server