Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

investigation_open

Read-only

Open a persisted investigation over a past time window, review collected evidence, and advance through diagnostic steps without contacting devices.

Instructions

[READ][risk=low] Open an investigation over one past window and walk what can be walked.

Contacts no device — the window is already past, and its evidence is whatever
was collected at the time. Each of the eight steps records its own outcome:
`done` (it ran, here is what it found), `refused` (it could not run HERE —
no samples, no alarm source; a site fact) or `not_possible` (this product
cannot do it at all).

The investigation is persisted, so it can be re-read and advanced later.

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": {
      "endpoint": "<endpoint>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "investigation_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
siteNodefault
assetNo
startYes
endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A4.2/5.0
Behavior5/5

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

The annotations already indicate readOnly/openWorld/non-destructive, and the description adds important non-obvious behavior: no device contact, evidence collected at the time, per-step outcomes, and persistence. These details go well beyond the structured fields and materially help an agent understand side effects and failure modes.

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 with [READ][risk=low]. Each sentence contributes a distinct fact: past window, no device contact, outcome semantics, and persistence. There is no filler.

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?

The description is behaviorally rich and partially compensates for the absent output schema by enumerating outcome states. However, with no output schema and 0% parameter documentation, it leaves endpoint/site/asset semantics and the identity of the eight steps unclear, so an agent has incomplete invocation detail.

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% and the description gives no direct parameter guidance. 'Past window' loosely implies start/end define the time range, but endpoint, site, and asset are left unexplained, and no formats or value constraints are provided. With five parameters, this is a substantial gap.

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 and object: 'Open an investigation over one past window and walk what can be walked.' It clearly distinguishes itself from sibling investigation tools by emphasizing the window is past and that no device is contacted. The outcome taxonomy (done/refused/not_possible) further clarifies what the tool produces.

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?

It provides clear usage context: use it for a past window, it does not contact a device, and it persists the investigation for later re-reading and advancement. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls just short of full routing guidance.

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