Skip to main content
Glama

filament_list_docs

Browse documentation sections for Filament admin panels to find component references and implementation guidance for Laravel framework versions.

Instructions

List documentation sections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNo5.x

Implementation Reference

  • The 'filament_list_docs' tool is defined as a server tool registration that returns documentation sections based on the provided version. The handler logic is directly implemented in the async callback function starting at line 188.
    server.tool("filament_list_docs", "List documentation sections", {
      version: versionSchema,
    }, async ({ version }) => {
      const sections = version === "4.x" ? documentationSections.v4 : documentationSections.v5;
      return { content: [{ type: "text", text: `# Docs Index (${version})\n\n${sections.map(s => `## ${s.category}\n${s.sections.map(sec => `- ${sec}`).join("\n")}`).join("\n\n")}` }] };
    });
Behavior2/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. 'List documentation sections' implies a read-only operation but doesn't specify what 'sections' means, whether there's pagination, rate limits, authentication requirements, or how results are structured. This leaves significant gaps for an agent to understand the tool's behavior.

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 extremely concise—just three words—and front-loaded with the core action. There's no wasted text, making it easy to parse, though this brevity comes at the cost of detail.

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 complexity (a listing tool with one parameter but no output schema or annotations), the description is incomplete. It doesn't cover what 'sections' entails, how results are returned, or the role of the 'version' parameter. With no annotations to fill gaps, this leaves the agent with insufficient context for reliable use.

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 one parameter ('version') with an enum and default value, but schema description coverage is 0%, meaning the schema itself provides no descriptive context. The description doesn't mention parameters at all, but since there's only one optional parameter with clear enum values, the baseline is high. However, it doesn't explain what 'version' refers to (e.g., Filament framework version) or how it affects the listing.

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 'List documentation sections' clearly states the verb ('List') and resource ('documentation sections'), providing a basic purpose. However, it doesn't differentiate from sibling tools like 'filament_get_docs' or 'filament_search_docs', leaving ambiguity about what distinguishes this listing operation from other documentation-related tools.

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. With multiple sibling tools related to documentation (e.g., 'filament_get_docs', 'filament_search_docs'), there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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