Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

investigation_list

Read-only

List saved investigations newest first to review prior OT alarm and downtime root-cause analyses, optionally filtered by site.

Instructions

[READ][risk=low] List saved investigations, newest first.

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

Input Schema

NameRequiredDescriptionDefault
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by stating the ordering behavior ('newest first') and that only saved investigations are returned, which are not visible in annotations or schema.

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 one short, front-loaded sentence with a useful READ tag prefix. Every word contributes meaning, and there is no redundant boilerplate.

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?

For a simple read-only list tool, the description covers the core action and ordering. However, the undocumented 'site' parameter is a real gap, and with no output schema or parameter guidance, the description is only minimally complete rather than fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention the 'site' parameter at all. An agent cannot determine whether 'site' filters results, groups them, or is required for certain contexts, so the description fails to compensate for the bare input schema.

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 uses a clear verb and resource: 'List saved investigations' plus an ordering detail ('newest first'). It distinguishes itself from siblings like investigation_show and investigation_open by focusing on listing rather than viewing or opening a specific investigation.

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 makes it clear that this tool is for listing saved investigations, which gives an agent a reasonable context for when to call it. It does not explicitly name alternatives or state when not to use it, but the action is straightforward enough that no exclusion is strictly required.

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