Skip to main content
Glama

Summarize log severity

bpj_summarize_log_severity
Read-onlyIdempotent

Count recognized severity prefixes in plain log lines, with optional timestamps, and report the unclassified lines.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "log": "<log>"
    },
    "name": "bpj_summarize_log_severity"
  }
}

Input Schema

NameRequiredDescriptionDefault
logYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral detail — it only counts *recognized* prefixes and separately reports unclassified lines, and tolerates optional timestamps — but it never says which prefixes count as recognized or what the returned counts look like.

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?

One sentence, front-loaded with the primary action and followed by the secondary reporting behavior; nothing is padded. It is slightly over-compressed, since 'recognized severity prefixes' is the key term and is never unpacked.

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?

With no output schema and no parameter descriptions, the description must cover both input and output expectations. It hints at the output (counts plus a list of unclassified lines) but does not specify the severity vocabulary or the result structure, leaving an agent to guess before calling.

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 coverage is 0% (the single `log` parameter has no description beyond a title and an 8000-char cap), so the description must carry the load. It does clarify that input is plain log lines with optional timestamps, which is real added meaning, but it leaves the line format, severity vocabulary, and size expectations largely implicit.

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 names a specific verb (count) and resource (recognized severity prefixes in plain log lines) plus a secondary output (unclassified lines), so the tool's function is unambiguous. It does not differentiate from siblings, but the siblings listed are unrelated single-purpose utilities, so the omission is minor.

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 narrow scope: feed it plain log text to get a severity tally. There is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as how lines should be formatted or what happens with already-parsed/structured logs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.