Skip to main content
Glama
vmware-skills

io.github.zw008/vmware-log-insight

alert_history

Read-onlyIdempotent

Retrieve recent trigger-history records for a fired alert, including timestamps and metadata. Use the truncated flag to detect omitted older records and raise the limit to fetch them.

Instructions

[READ] List recent trigger-history records for an alert.

Use this for when an alert fired, not how it's defined. Returns the family list envelope {items, returned, limit, total, truncated, hint}; each item is {timestamp_ms, info}. total is the real history-record count, so truncated answers whether older records were left behind — raise limit when true. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum history records returned, most recent first as the appliance orders them (default 50). There is no offset — the appliance hands back the whole history in one call and this slices it, so when truncated is true the only way to reach older records is a larger limit.
targetNoLog Insight target name as spelled in ~/.vmware-log-insight/config.yaml. Omit to use that file's default_target — with no default configured, omitting it is an error that lists the configured names.
alert_idYesThe alert id exactly as returned in an alert_list row's 'id' field (not the alert's name). An empty string is refused with a message telling you to run alert_list first.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / alert_id / description
      Added value: +"The alert id exactly as returned in an alert_list row's 'id' field (not the alert's name). An empty string is refused with a message telling you to run alert_list first."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum history records returned, most recent first as the appliance orders them (default 50). There is no offset — the appliance hands back the whole history in one call and this slices it, so when truncated is true the only way to reach older records is a larger limit."
    • addedInput schema / properties / target / description
      Added value: +"Log Insight target name as spelled in ~/.vmware-log-insight/config.yaml. Omit to use that file's default_target — with no default configured, omitting it is an error that lists the configured names."
  2. First observedv1.8.9

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses the exact return envelope, item shape, and the semantics of 'total' and 'truncated' — including the actionable 'raise limit when true' behavior. This goes well beyond the annotations' readOnlyHint and gives the agent operational understanding of the tool's output.

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 compact and front-loaded: a [READ] tag, a clear purpose sentence, a usage note, and a return-format explainer. Every sentence contributes value, and nothing is wasted or redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully documents the return envelope and item fields, plus the truncation/limit behavior. Combined with a 100%-covered input schema, an agent has everything needed to call this tool correctly and interpret its results.

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 baseline is 3. The description reinforces the limit/truncated relationship, but the input schema already explains it in detail; the description adds no new parameter-level meaning beyond what the schema provides.

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 opens with a specific verb-resource pair: 'List recent trigger-history records for an alert.' It also disambiguates from sibling tools by clarifying this concerns when an alert fired ('trigger-history') rather than how it's defined, which clearly separates it from alert_list and alert_get.

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

Usage Guidelines5/5

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

The statement 'Use this for when an alert fired, not how it's defined' is an explicit when/when-not guardrail. It tells the agent to choose this tool for firing events, not definition/configuration, and directs the agent away from definition-focused siblings without needing to inspect schemas.

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

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/vmware-skills/VMware-Log-Insight'

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