Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

investigation_show

Read-only

Retrieve a saved investigation and review its stored state to resume analysis from where it was left.

Instructions

[READ][risk=low] Re-read a saved investigation — the state it was left in.

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": {
      "investigation_id": "<investigation_id>"
    },
    "name": "investigation_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
investigation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's '[READ][risk=low]' mostly repeats that. It adds some behavioral context with 'the state it was left in,' indicating the tool returns the previously saved snapshot, but it does not disclose details like error behavior or what happens for missing/invalid investigation IDs.

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?

One concise sentence with no wasted words, and the read/risk profile is front-loaded. It conveys the core purpose and key distinguishing detail efficiently.

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?

This is a simple one-ID read tool with annotations covering safety, so the bar is lower. However, with no output schema, the description only vaguely indicates the return ('the state it was left in') and does not explain what fields or format the saved investigation state will be returned in. It is minimally adequate but leaves a small 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?

Schema description coverage is 0%, so the description needs to compensate. It does not explicitly define investigation_id beyond the schema's 'Investigation Id' title, though the phrase 'a saved investigation' implies the ID refers to a previously saved investigation. The single parameter is self-explanatory enough, but the description adds little direct semantic detail beyond the 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 specific verb ('Re-read'), a clear resource ('a saved investigation'), and a distinctive semantic ('the state it was left in'). This differentiates it from siblings like investigation_open and investigation_list, which involve opening or listing rather than re-reading a saved investigation by ID.

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 phrase 'a saved investigation' implies this is for resuming or inspecting an existing investigation, but the description does not explicitly say when to use it over investigation_open or investigation_list, nor does it mention when not to use it. Usage guidance is mostly implied rather than stated.

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