Skip to main content
Glama

list_components

Lists all available component names for use with the get_component tool, enabling quick selection of UI elements.

Instructions

Lists all available component names you can pass to get_component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_components' tool. It returns a list of all component names grouped by category (Navigation, Header, Tabs, Content, ActionBar, Reports, Overlay, Forms, Tokens). It does not take any input arguments and returns a text content block with the grouped component listing.
    server.tool("list_components", "Lists all component names you can pass to get_component(). Grouped by category.", {}, async () => {
      const grouped: Record<string, string[]> = {
        Navigation: ["topnavbar","sidemenu-settings","sidemenu-reports","line-tab","line-tab-quicklink"],
        Header: ["header-v1","header-v2","header-v3"],
        Tabs: ["classic-tab","line-tab"],
        Content: ["data-table","data-table-type2","widget","stat-card","button-row","note-container"],
        ActionBar: ["actionbar-type1","actionbar-type2","actionbar-type8"],
        Reports: ["rpt-chart-floater"],
        Overlay: ["drawer-sm","drawer-md","drawer-lg"],
        Forms: ["form-text","form-textarea","form-checkbox","form-radio","form-dropdown"],
        Tokens: ["design-tokens"],
      };
      const text = Object.entries(grouped).map(([g, ns]) => `**${g}**\n${ns.map(n => `  - ${n}`).join("\n")}`).join("\n\n");
      return { content: [{ type: "text" as const, text }] };
    });
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 says 'lists all available component names,' which is adequate for a read-only list operation. However, it does not mention whether the list is sorted, paginated, or has any limits.

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 (10 words), front-loaded with the action, and no unnecessary words. It is perfectly concise.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema), the description is complete. It references a sibling tool for context and explains the value of the output.

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 input schema has zero parameters with 100% coverage, so no additional parameter info is needed. Baseline score of 4 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 clearly states the tool's action: listing component names. It specifies the output is to be passed to a specific sibling tool (get_component), which distinguishes its purpose from other list/get tools.

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 implicitly guides the agent to use this tool before get_component. It does not explicitly state exclusions or alternatives, but for a simple listing tool, the context is clear enough.

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/Anguraj-zoho/elegant-mcp'

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