Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

line_relation_declare

Read-only

Declare which asset feeds another to establish line order for root-cause analysis and avoid downstream false causes.

Instructions

[READ][risk=low] Record that one asset feeds another — the second RCA axis.

`[READ]` follows this repo's convention, where the tag is about PLANT state:
it touches no device, exactly like `baseline_record_change` and
`adopt_alias_map`, which are the same shape. It does write — a declaration
about the line, into the site knowledge base.

With time alone, an upstream stoppage produces a string of equally-confident
downstream false causes, because on a line downstream co-occurrence is
guaranteed whatever the cause. That guarantee is exactly why this is a
declaration and not something inferred (D25): a person stating the line
order needs no inference at all.

``by`` is required — a person is the evidence, and an edge with no author is
indistinguishable from a guess a year later. Self-loops and cycles are
refused here, where somebody can still fix them.

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": {
      "upstream": "<upstream>",
      "downstream": "<downstream>",
      "by": "<by>"
    },
    "name": "line_relation_declare"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
siteNodefault
upstreamYes
downstreamYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

B3.2/5.0
Behavior1/5

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

The description explicitly says 'It does write — a declaration about the line, into the site knowledge base,' while annotations carry readOnlyHint: true. This is a direct contradiction and forces an agent to guess whether side effects occur. The added details about `by` and cycle rejection are useful but cannot offset the contradictory read/write signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The summary is front-loaded in one sentence, followed by organized paragraphs on convention, rationale, and constraints. It is longer than strictly necessary due to the root-cause reasoning, but each paragraph earns its place and the structure helps an agent parse the key points.

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 four-parameter write-like tool with no output schema and no parameter descriptions, the description covers purpose, direction, author requirement, and cycle restriction. But it omits what the call returns, the role/default of `site`, and how asset identifiers are expressed, and the read/write contradiction leaves a core uncertainty.

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?

With 0% schema description coverage, the description must compensate. It gives direction meaning to upstream/downstream ('one asset feeds another'), explains why `by` is required, and notes cycles are refused. However, it never describes the `site` parameter or value formats, so not all parameters receive adequate semantic coverage.

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 opening sentence 'Record that one asset feeds another' names a specific verb and resource, and the rest clarifies it is a person-authored declaration about line order rather than an inference. It is clear about the core operation, though it does not explicitly contrast itself with the sibling line_relations_list or other RCA tools.

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 gives useful context: a person is the evidence, this is a declaration rather than something inferred, and self-loops/cycles are refused. However, it does not explicitly name alternative tools or state a when-not-to-use condition.

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