Skip to main content
Glama

history

Retrieve anomalies recorded in the last N days from the local profile store for the configured connection, without re-profiling the warehouse.

Instructions

Return anomalies recorded in the last days days (capped).

Reads from the local profile store — does not re-profile the warehouse. Only the configured connection's anomalies are returned. They carry the same fields as watch; those recorded before the fields existed have them all null.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavioral burden and does add useful context: it reads from the local profile store, avoids re-profiling the warehouse, only returns anomalies for the configured connection, and explains that older records may have null fields. It still leaves the cap unspecified and does not explicitly state read-only behavior, permissions, or failure conditions.

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?

The description is front-loaded with the core action and then adds only context that matters: local-store source, no re-profiling, connection scope, and legacy null fields. Every sentence contributes useful information without filler or repetition.

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?

For a simple read-only history tool with an output schema, the description is largely complete: it covers data source, scope, and legacy field behavior, so return-field details are not needed. It still omits explicit usage routing among siblings and the meaning of the cap, which leaves a modest but real gap.

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?

The single `days` parameter has no schema description, so the description must compensate. It does clarify that `days` is a lookback window and that results are capped, but it does not explain the cap value, the schema default of 30, or valid ranges. This is partial compensation rather than complete parameter guidance.

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 and resource: it returns anomalies recorded in the last `days` days. It also distinguishes itself from profiling behavior by stating that it reads from the local profile store and does not re-profile the warehouse. The remaining gap is that the generic name `history` and the lack of explicit routing among siblings leave some purpose differentiation implicit.

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?

The description implies when to use the tool by saying it reads local history and does not re-profile the warehouse, which suggests use for retrieving past anomalies without a new profiling run. However, it never explicitly compares this to `watch`, `investigate`, `check`, or the other siblings, and it provides no exclusions or prerequisites.

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