Skip to main content
Glama

filament_get_commands

Retrieve Filament artisan commands to manage admin panel development and operations within Laravel applications.

Instructions

Get Filament artisan commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNo5.x

Implementation Reference

  • The implementation and registration of the "filament_get_commands" tool. It retrieves artisan commands based on the requested Filament version from the `artisanCommands` data source.
    server.tool("filament_get_commands", "Get Filament artisan commands", {
      version: versionSchema,
    }, async ({ version }) => {
      const commands = version === "4.x" ? artisanCommands.v4 : artisanCommands.v5;
      return { content: [{ type: "text", text: `# Filament ${version} Commands\n\n\`\`\`bash\n${commands.map(c => `${c.command}  # ${c.description}`).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. It states the action ('Get') but doesn't describe what 'Get' entails—whether it lists, retrieves details, or executes commands, nor does it cover permissions, rate limits, or output format. This lack of detail is a significant gap for a tool with no annotation coverage, making it hard to predict 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—a single phrase 'Get Filament artisan commands'—with zero wasted words. It's front-loaded and directly states the purpose without unnecessary elaboration, making it efficient for quick understanding. This is ideal for conciseness in tool descriptions.

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 (low, with 1 parameter) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'artisan commands' are, how results are returned, or any behavioral traits. For a tool in a set with many siblings, more context is needed to ensure the agent can use it correctly without trial and error.

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 description adds no parameter semantics beyond the input schema, which has 1 parameter ('version') with 0% schema description coverage. However, since there's only 1 parameter and it has an enum (['4.x', '5.x']) with a default ('5.x'), the schema itself provides clear constraints. The description doesn't need to compensate heavily, but it also doesn't explain what 'version' means in context (e.g., Filament framework version). Baseline is high due to low parameter count and schema clarity.

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 tool's purpose: 'Get Filament artisan commands' specifies both the verb ('Get') and resource ('Filament artisan commands'). It distinguishes from siblings like 'filament_get_docs' or 'filament_list_components' by focusing on commands rather than documentation or components. However, it doesn't explicitly differentiate from all siblings (e.g., 'filament_discover_docs' might also involve commands), so it's not a perfect 5.

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 prerequisites, context (e.g., Laravel/Filament environment), or comparisons to siblings like 'filament_generate_plan' or 'filament_search_docs'. Without any usage instructions, it leaves the agent to infer applicability, which is insufficient for effective tool 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