Skip to main content
Glama

handoff_profile

Summarize log files by counting line patterns without loading them into context. Get counts, first/last lines, value spreads, and full rare lines with real line numbers to target the lines that matter.

Instructions

Summarize log files by counting, with no model, so you do not read them into your own context. Each kind of line is shown once with its count, first and last line, and the spread of its values (with any odd one out and the first big jump in a number); lines that happen only a few times are listed in full. Line numbers are real: Read the lines that matter before acting on them.

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": {
      "paths": "<paths>"
    },
    "name": "handoff_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoOptional folder to show paths relative to.
pathsYesAbsolute file or folder paths.
includeNoOptional file name patterns for folders, e.g. ["*.py"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 well: it discloses the algorithm is model-free/deterministic, describes the aggregation output including outliers and the first large numeric jump, notes rare lines are listed in full, and confirms line numbers are real. Missing are operational traits such as traversal depth for folders, size limits, cost, and error behavior.

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?

The lead sentence is front-loaded and states purpose plus the context-saving rationale in one stroke. Subsequent sentences describe the return format efficiently, though some phrasing ('the first big jump in a number') is dense and would benefit from a touch more precision.

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?

There is no output schema, so the description must explain returns, and it does so in useful detail for a summarization tool. With three fully documented parameters and no annotations, the remaining gaps are operational (limits, folder traversal, errors) rather than anything blocking correct invocation.

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 the schema already explains paths, root, and include. The description adds no parameter-specific meaning (e.g., how include patterns interact with folder recursion or what root affects beyond presentation), so the baseline of 3 applies.

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 states a specific verb and resource: count-summarize log files without loading them into the agent's context. It also sketches the output shape (per-line-kind counts, first/last line, value spread), which makes the tool's role distinct. It stops short of naming the sibling read tool explicitly, so the differentiation from handoff_read is implied rather than stated.

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?

Usage is clear from context: profile first so the raw files do not enter context, then 'Read the lines that matter before acting on them,' which implies a follow-up read step. There are no explicit exclusions (e.g., binary files, very large trees, whether folders recurse), which keeps this below a 5.

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