Skip to main content
Glama

chimera_log_compress

Compress build/test/install logs by removing redundant lines while keeping every error, warning, and traceback. Retains head and tail for context, reducing log size 80-95% without losing diagnostic information.

Instructions

Compress build/test/install logs while preserving every error, warning, and traceback line verbatim. Keeps head + tail windows for context. Typical reduction 80-95% on noisy logs with zero loss of diagnostic signal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesRaw log output.
keep_patternsNoCase-insensitive substrings; lines containing any of these are kept verbatim. Defaults to error/warn/fail/exception/traceback patterns.
head_linesNo
tail_linesNo
context_linesNoNumber of lines to keep on each side of every matched line.
auto_trackNoRecord token savings to chimera_dashboard.
modelNoclaude-sonnet-4-6
namespaceNodefault
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions reduction metrics and zero diagnostic loss, but lacks details on where compressed logs go, side effects, or recording behavior beyond auto_track.

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 concise sentences front-load the purpose and provide key details without wasted words.

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?

While covering main functionality, the description omits what the tool returns (output format), which is important given no output schema is provided.

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 50%. The description adds meaning by mentioning head/tail windows and preserved patterns, but does not explain parameters like auto_track, model, or namespace, leaving gaps.

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?

The description clearly states the tool compresses logs while preserving errors, warnings, tracebacks, and head/tail windows. It uses specific verbs and resource, distinguishing it from sibling tools like chimera_compress.

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

Usage Guidelines4/5

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

The description specifies the use case for build/test/install logs, providing clear context. However, it does not explicitly mention when not to use it or list alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fernandogarzaaa/chimeralang-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server