Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read-only access to this site's error logs and captured fatal errors. Call status first. Only answers while WordPress can still boot; a fully white-screened site is unreachable here.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
statusA

Whether PHP error logging and fatal-error capture are on, the WP_DEBUG flags, log sizes, whether alerts are set up, and when the last fatal error happened. Start here.

list_log_sourcesA

List the log sources FatalGuard can read on this site (PHP error log, wp-content/debug.log, PHP ini error_log, etc.) with size and whether they are readable. Use the returned id with tail_log or list_errors.

tail_logA

Return the newest lines of a log source (by id from list_log_sources), oldest first, secrets redacted, optionally only lines containing a text. Use to read raw log context around an error.

list_errorsA

Errors of a log grouped by signature, newest first: level, message, file and line, count, first and last seen. Use for "what keeps failing" questions.

list_recent_fatalsA

Captured fatal errors (white screens) grouped, newest first: signature, message, file and line, the plugin or theme that caused it, count, first and last seen. Use this to see what is currently crashing the site; pass a signature to get_fatal for details.

get_fatalA

The latest record of one fatal-error group (signature from list_recent_fatals): full message incl. stack trace, file, line, origin, URL, PHP version, and its last occurrences.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clearly distinct purposes: status is an overview, list_log_sources discovers sources, tail_log reads raw lines, and get_fatal drills into one fatal group. The only potential confusion is between list_errors (grouped errors from a log source) and list_recent_fatals (grouped captured fatals), but their descriptions and required inputs make the boundary reasonably clear.

Naming Consistency4/5

Five of six tools follow a clear verb_noun or list_* pattern (list_log_sources, list_errors, list_recent_fatals, tail_log, get_fatal). The bare noun 'status' is a minor deviation, though it reads naturally as an overview entry point.

Tool Count5/5

Six tools is well-scoped for a read-only fatal-error and log diagnostics server. Each tool serves a distinct step in the workflow (overview, source discovery, raw tail, grouped errors, grouped fatals, fatal detail) with no obvious padding.

Completeness4/5

The surface covers the core diagnostic lifecycle: status, source discovery, raw log reading, grouped error listing, grouped fatal listing, and fatal detail. Minor gaps exist—there is no detail tool for an individual non-fatal error group and no explicit way to acknowledge or clear errors—but agents can work around these with the existing tools.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues