Skip to main content
Glama

filament_list_components

Lists all available components within a specific Filament category to help developers find and implement UI elements for admin panels.

Instructions

List all components in a category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
versionNo5.x

Implementation Reference

  • The handler for 'filament_list_components' retrieves component lists from either Filament V4 or V5 references based on the provided version and category.
    server.tool("filament_list_components", "List all components in a category", {
      category: z.enum(["forms", "tables", "infolists", "actions", "schemas", "support"]),
      version: versionSchema,
    }, async ({ category, version }) => {
      const reference = version === "4.x" ? filamentV4Reference : filamentV5Reference;
      const found = reference.categories.find(c => c.slug.toLowerCase() === category.toLowerCase());
      if (!found) return { content: [{ type: "text", text: `Category "${category}" not found.` }] };
      return { content: [{ type: "text", text: `# ${found.name} Components\n\n${found.components.map(c => `- **${c.name}**: ${c.description}`).join("\n")}` }] };
    });
Behavior1/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 of behavioral disclosure. It only states the action without details on permissions, rate limits, output format, pagination, or side effects. For a list operation with zero annotation coverage, this is inadequate and fails to inform the agent about how the tool behaves.

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, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core action, making it easy to parse quickly, though it lacks depth.

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?

Given the tool's complexity (2 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, error handling, or how parameters interact, leaving significant gaps for the agent to infer behavior, which reduces effectiveness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description mentions 'category' but doesn't explain what it means or list the enum values. It omits the 'version' parameter entirely. This adds minimal semantic value beyond the bare schema, failing to compensate for the low coverage.

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

Purpose3/5

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

The description states the action ('List') and target ('components in a category'), which clarifies the basic purpose. However, it's vague about what 'components' are (e.g., UI components, code modules) and doesn't distinguish this from sibling tools like 'filament_get_component' or 'filament_list_docs', missing specificity for a 4-5 score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools (e.g., 'filament_get_component' for details or 'filament_search_docs' for broader searches) or any context like prerequisites, making it minimally helpful for selection.

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/serbansorin/filament-mcp-server'

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