Skip to main content
Glama
Sign In
FatalGuard

FatalGuard

by zinoodev85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

list_recent_fatals

Lists recent fatal errors grouped newest first, showing message, file/line, culprit plugin or theme, and counts so you can identify what is crashing the site; pass a signature to retrieve details.

Instructions

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.

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": "list_recent_fatals"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many fatal groups to return (1-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
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 ordering (newest first), grouping semantics, and the full set of returned fields, which is substantial behavioral context. It stops short of stating read-only behavior, truncation limits, or whether groups are deduplicated across time windows.

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?

Two sentences, zero filler: the first front-loads what is returned and in what order, the second gives usage and the hand-off. Nothing is repeated from the schema or restated from the name.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates by enumerating the returned fields and their ordering, and by pointing to get_fatal for detail. That is enough for an agent to call this correctly and interpret the result.

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?

There is a single optional parameter and schema description coverage is 100% ('How many fatal groups to return (1-100)' with default 20 and bounds). The description adds no meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Captured fatal errors (white screens) grouped, newest first') plus the exact grouping keys returned (signature, message, file/line, culprit plugin/theme, count, first/last seen). This clearly separates it from list_errors and tail_log, which are not grouped fatal signatures.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('see what is currently crashing the site') and names the alternative plus the condition that selects it ('pass a signature to get_fatal for details'). The agent does not need to infer the drill-down path from sibling names alone.

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