Skip to main content
Glama

log_summary

Read-only

Summarize logs of any size into levels, time spans, errors first, frequent message patterns, and stack traces to speed troubleshooting.

Instructions

Summarize a log (any size): levels, time span, errors first, frequent message patterns with lines and stack traces.

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

Input Schema

NameRequiredDescriptionDefault
topNo
pathNoor a file
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/5.0
Behavior4/5

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

With only readOnlyHint=true supplied, the description carries most of the behavioral load, and it does disclose the result composition and ordering ('errors first', patterns with lines and stack traces). It is silent on how file vs inline text input is treated, on precedence if both are given, and on truncation behavior despite the 'any size' claim.

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?

A single front-loaded sentence with a colon-delimited list of what the summary contains; no filler and nothing that could be trimmed without losing information.

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

Completeness3/5

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

The description adequately conveys the output shape for a tool with no output schema, but with three loosely documented parameters and no annotations beyond readOnlyHint, it leaves key invocation details (top's meaning, path vs text handling) for the agent to guess.

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

Parameters2/5

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

Schema coverage is only 33% (just path described as 'or a file'), and the description adds no meaning for 'top' (presumably a limit on patterns) or 'text' (inline log content). It also does not explain the relationship or precedence between path and text.

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 gives a specific verb (summarize) and resource (a log) and enumerates what the summary contains: levels, time span, errors, frequent message patterns with lines and stack traces. That is enough to distinguish it from siblings like extract, diff, or json, none of which are log summarizers, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The only usage hint is '(any size)', which suggests it is safe for large inputs, but there is no statement of when to pick this over alternatives, no prerequisites, and no guidance on choosing between the path and text inputs or when both might be supplied.

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