Skip to main content
Glama

list_all_components

Retrieve all available PrimeNG UI components with brief descriptions to explore options for Angular development.

Instructions

Lista todos los componentes disponibles en PrimeNG con una breve descripción

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The ListComponentsTool class provides the core handler implementation for the 'list_all_components' tool. The constructor sets the tool name, and the execute method generates the formatted list of components using COMPONENT_CATEGORIES.
    export class ListComponentsTool extends BaseTool {
      constructor() {
        super('list_all_components');
      }
    
      async execute(_args: Record<string, any>): Promise<ToolResponse> {
        return this.createResponse(formatComponentList(COMPONENT_CATEGORIES));
      }
    }
  • Function that defines the JSON schema for the list_all_components tool, specifying name, description, and empty input schema.
    export function createListAllComponentsSchema(): Tool {
      return {
        name: "list_all_components",
        description: "Lista todos los componentes disponibles en PrimeNG con una breve descripción",
        inputSchema: {
          type: "object",
          properties: {},
        },
      };
    }
  • Registration and dispatching logic in the MCP CallToolRequestSchema handler's switch statement, calling the tool instance's run method.
    case "list_all_components":
      return await this.listComponentsTool.run(args);
  • The tool schema is registered in the ListToolsRequestSchema handler's tools array.
    createListAllComponentsSchema(),
  • Instantiation of the ListComponentsTool class instance used for handling tool calls.
    this.listComponentsTool = new ListComponentsTool();
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 only states what the tool does, not how it behaves. It doesn't mention response format, pagination, rate limits, authentication needs, or error handling. The description adds no behavioral context beyond the basic operation.

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, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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 read-only listing tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned (beyond 'brief description'), format, structure, or any limitations. The context signals indicate this tool needs more complete documentation.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for this dimension.

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 ('Lista todos los componentes') and target resource ('componentes disponibles en PrimeNG'), with additional detail about including brief descriptions. It doesn't explicitly differentiate from sibling tools like 'search_components', but the purpose is unambiguous.

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_components' or 'get_component_doc'. The description implies a comprehensive listing, but lacks explicit usage context or exclusions.

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/hnkatze/PrimeNG_MCP'

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