Skip to main content
Glama

parse_server_log

Extracts integration status, duration, deduplicated errors/warnings, execution timeline, and XSLT cc:log messages from Workday server logs while suppressing boilerplate and sensitive config data.

Instructions

Parses a Workday server log (server-{eventId}.log) and returns a focused summary: integration status, duration, deduplicated errors/warnings, execution timeline, and any XSLT cc:log messages.

The raw log is 10-15k lines of framework boilerplate and XML config dumps (which contain plaintext credentials and are never surfaced). This tool extracts the signal and suppresses the noise.

If log_path is omitted, searches ~/Downloads for the most recently modified server-*.log file.

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

Input Schema

NameRequiredDescriptionDefault
log_pathNoAbsolute path to the server log file. If omitted, the most recent server-*.log in ~/Downloads is used.
show_warningsNoInclude WARN entries in the errors section (default: true). Set false to show only ERRORs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the raw log is 10-15k lines of boilerplate, that XML config dumps contain plaintext credentials and are never surfaced, that errors/warnings are deduplicated, and that WARN entries are included by default. It stops short of stating whether the tool is read-only and what happens on a missing or malformed log file.

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?

Three short paragraphs, front-loaded with the core action and return contents, then rationale, then the default-path rule. Every sentence carries information; the 'extracts the signal and suppresses the noise' line is slightly redundant with the preceding enumeration but is not wasteful.

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 2-parameter tool with no output schema, the description compensates well by describing the shape of the returned summary and the credential-suppression behavior. Remaining gaps are minor: failure behavior for a nonexistent path and whether large outputs are truncated.

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 description coverage is 100%, so both parameters are already documented, including the show_warnings default and the ~/Downloads fallback. The description reinforces the omitted-path behavior and frames why log_path matters (log files are large and noisy), but adds no syntax, format, or validation detail beyond the schema — baseline 3 is appropriate.

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?

States a specific verb and resource ('Parses a Workday server log (server-{eventId}.log)') and enumerates exactly what the returned summary contains (integration status, duration, deduplicated errors/warnings, timeline, XSLT cc:log messages). It does not name or contrast with the plausible sibling log_learning, so an agent must still infer which log-related tool applies.

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?

Usage is implied by the resource type: call it when you have a server-{eventId}.log to interpret. The description gives one concrete operational rule (if log_path is omitted, the most recent server-*.log in ~/Downloads is used) but offers no when-not guidance and no comparison to alternatives such as log_learning.

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