Skip to main content
Glama
iMateo

fastpanel-mcp

by iMateo

site_logs

Tail nginx or Apache access and error logs directly to debug site issues such as 404 errors, permission problems, or PHP-FPM failures.

Instructions

Tail a site's nginx/apache access or error log — no SSH needed. Maps to GET /api/sites/{site_id}/log/{lines}/{type}. Use type=frontend_error to debug 404/permission/realpath problems (nginx), backend_error for PHP-FPM/Apache app errors. FastPanel quirk: this endpoint returns the log tail inside an 'errors' JSON field and responds with HTTP 400 even on success — an empty log shows as '\n', a missing file shows a 'Path … not exists' message. This tool normalises that: the log text is always returned under log, and 400 is not treated as a failure. Log files live at /data/logs/-.log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNofrontend_* = nginx, backend_* = PHP-FPM/Apache; *_error for diagnostics, *_access for trafficfrontend_error
linesNoNumber of trailing lines to return
site_idYesSite id from sites_list
Behavior4/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 discloses the FastPanel quirk (log text in 'errors' field, HTTP 400 on success), empty log behavior, and missing file behavior. This is highly transparent, though rate limits or authentication are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise, front-loading the main purpose. The quirk explanation is necessary but slightly lengthy. Overall well-structured with no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return value structure ('log' field) and edge cases (empty, missing). It also covers the endpoint mapping. Completeness is high, though live streaming or max line limit are not mentioned (schema covers limit).

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds context for the 'type' parameter (explaining enum values) and endpoint mapping, adding some value beyond the schema.

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

Purpose5/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: tailing nginx/apache logs without SSH. It specifies the resources (access/error logs) and distinguishes from sibling tools which are mostly unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance on when to use specific log types (frontend_error for nginx, backend_error for PHP-FPM/Apache) and explains the quirky API behavior. It does not explicitly state when not to use the tool, but the guidance is clear enough.

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/iMateo/fastpanel-mcp'

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