Skip to main content
Glama
Sign In
FatalGuard

FatalGuard

by zinoodev85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

status

Check whether PHP error logging and fatal-error capture are enabled, review WP_DEBUG flags, log sizes, alert setup, and the last fatal error.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the categories of information inspected, which suggests a read-only status check, but it never explicitly states read-only behavior, side effects, permissions, or response format.

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 compact sentence listing the relevant status dimensions, followed by a short call to action. Every clause contributes to describing the tool's output scope, and the entry-point guidance is front-loaded enough.

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?

For a zero-parameter, annotation-free status tool with no output schema, the description enumerates the key reported dimensions an agent would need in order to decide whether to call it. It could be slightly more complete by stating the read-only nature or response structure, but it is sufficient for this low-complexity tool.

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 tool has zero parameters and the schema coverage is 100%, so there is no parameter semantics burden. Baseline 4 is appropriate because there are no inputs to explain.

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 specifies a concrete status/overview resource: PHP error logging state, fatal-error capture, WP_DEBUG flags, log sizes, alert setup, and last fatal error timing. It is clearly an aggregate health/status check rather than a log retrieval tool, which distinguishes it from siblings like get_fatal and list_errors.

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

Usage Guidelines3/5

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

"Start here" gives a clear entry-point recommendation, implying this is the first diagnostic call. However, it does not explicitly state when not to use it or name an alternative sibling for follow-up actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools