Skip to main content
Glama

history_report

Generates a self-contained HTML report of agent conversation analytics, friction points, cross-agent comparison, and skill or rule candidates, saved locally with no model calls.

Instructions

Write a self-contained HTML report (analytics, friction, cross-agent comparison, skill and rule candidates) to ~/.agent-history-mcp/reports and return its path. Local only; no model calls.

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

Input Schema

NameRequiredDescriptionDefault
projectNo
sourcesNoall
days_backNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description still discloses meaningful behavior: it writes a file to a concrete path, the report is self-contained HTML, it is local-only, and it makes no model calls — important for cost and privacy expectations. It omits other behavioral facts an agent would want, such as whether an existing report is overwritten, how the filename is derived, and whether the write can fail on permissions.

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?

Two tight sentences, front-loaded with the action and artifact, and the parenthetical content list earns its space by telling the agent what the report covers. The trailing 'Local only; no model calls' is compact and high-value, though the phrasing is slightly telegraphic.

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?

An output schema exists, so the return path needs no further explanation, and the description is complete on artifact type and execution locality. However, for a three-parameter scoping tool with zero schema documentation, the description leaves the entire input contract unexplained, which is a material gap for correct invocation.

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 description coverage is 0% for all three parameters, so the description carries the full burden and adds nothing: 'project', 'sources' (default 'all', accepting a string or array) and 'days_back' are never explained. An agent cannot tell what a source string means, what omitting 'project' scopes to, or how days_back interacts with the report sections named.

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 artifact ('Write a self-contained HTML report') and enumerates what the report contains (analytics, friction, cross-agent comparison, skill and rule candidates), plus the destination directory and the return value (the path). It implicitly contrasts with data-returning siblings like analyze_sessions and compare_sessions by producing a file artifact, but never names an alternative explicitly.

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 inferable rather than stated: an agent can deduce this is the tool for producing a shareable HTML artifact instead of raw analysis output. There is no explicit when-to-use, when-not-to-use, or named alternative, so selection against compare_sessions or analyze_sessions still requires inference.

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