Skip to main content
Glama

filament_get_docs

Fetch official Filament PHP documentation for specific categories and sections to implement admin panel components using Laravel's Filament framework.

Instructions

Fetch documentation from filamentphp.com

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
sectionYes
versionNo5.x

Implementation Reference

  • The handler implementation for the `filament_get_docs` tool, which fetches documentation pages from filamentphp.com using `fetchDocPage`.
    server.tool("filament_get_docs", "Fetch documentation from filamentphp.com", {
      category: z.string().min(1),
      section: z.string().min(1),
      version: versionSchema,
    }, async ({ category, section, version }) => {
      try {
        const doc = await fetchDocPage(version, category, section);
        if (!doc) {
          return {
            content: [{
              type: "text",
              text: `# Documentation Not Found\n\nAttempted URL: ${getDocUrl(version, category, section)}\n\nTry using \`filament_list_docs\` to see known sections, or \`filament_discover_docs\` for live routes.`,
            }],
          };
        }
    
        return { content: [{ type: "text", text: `# ${doc.title}\n\nURL: ${doc.url}\n\n${doc.sections.map(s => `## ${s.title}\n\n${s.content}`).join("\n\n")}` }] };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: formatErrorMessage("Documentation Fetch Failed", error, "Retry later or query a different category/section."),
          }],
        };
      }
    });
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. It only states the action ('fetch') without disclosing behavioral traits like rate limits, authentication needs, response format, or error handling. This is inadequate for a tool with parameters and no output schema.

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 with zero waste. It's appropriately sized and front-loaded, though this conciseness 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 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how parameters interact, or behavioral context, making it insufficient for effective use.

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 description must compensate, but it adds no meaning beyond the schema. Parameters 'category', 'section', and 'version' are undocumented in both schema and description, leaving their semantics unclear (e.g., what categories or sections exist).

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 'Fetch documentation from filamentphp.com' states a clear verb ('fetch') and resource ('documentation'), but it's vague about scope and doesn't differentiate from sibling tools like 'filament_list_docs' or 'filament_search_docs'. It lacks specificity about what exactly is fetched.

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 on when to use this tool versus alternatives. With siblings like 'filament_list_docs' and 'filament_search_docs', the description offers no context for choosing between them, leaving the agent to guess based on tool names alone.

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