Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

line_relations_list

Read-only

Retrieve the declared line order for a site and identify what each asset feeds to support OT topology and dependency analysis.

Instructions

[READ][risk=low] The declared line order for a site, and what each asset feeds.

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

Input Schema

NameRequiredDescriptionDefault
siteNodefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

B3.3/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] tag repeats that safety profile. It adds a little context by specifying that results are based on declared order and feed relationships, but it does not disclose open-world behavior, default-site handling, or what happens when no declarations exist. No contradiction with annotations.

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 short sentence plus a safety tag, with no filler. The essential content—declared order and feed relationships—is front-loaded and every word earns its place.

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 one-optional-parameter read-only list tool, this is a minimally viable description. It tells an agent what the tool returns, but with no output schema it omits the return shape, the effect of omitting site, and any relationship to line_relation_declare.

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%, so the description should compensate for the undocumented site parameter, but it only repeats that the data is 'for a site.' It does not explain accepted site values, the meaning of the 'default' value, or how the parameter changes the response.

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 identifies a specific resource—the declared line order for a site—and adds that each asset's feed relationship is included, so the purpose of returning line-relation data is clear. It does not explicitly contrast itself with sibling line_relation_declare, but the read-only wording and the tool name make the distinction reasonably inferable.

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 word 'declared' implies this tool reads previously declared line relations, and the sibling name line_relation_declare hints at the complementary write operation. However, the description gives no explicit when-to-use guidance, prerequisites, or direct comparison with alternatives.

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