Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

mechanism_library_check

Read-only

Checks a mounted fault-mechanism library for a candidate cause, showing if its mechanisms apply, are excluded for this equipment, or are unknown so missing knowledge is not treated as clearance.

Instructions

[READ][risk=low] What a mounted fault-mechanism library says about one candidate cause.

Three answers, and the difference between the first two is the whole point:

* ``nothing_known`` — the library has never heard of this cause. **Not** "no
  objection": a knowledge base that knows nothing about something has not
  cleared it.
* ``known``, not excluded — mechanisms for it apply here, with what would
  confirm each.
* ``known``, excluded — every mechanism for it is inapplicable to this
  equipment, so the candidate can be ruled out. That is the strong move a
  ranker cannot make.

It never confirms. Raising a candidate to `confirmed` comes from outside the
ranking — a measurement, a reproduction, or a person (D29).

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": {
      "cause": "<cause>"
    },
    "name": "mechanism_library_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNodefault
causeYes
protocolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains the operational meaning of open-world semantics: nothing_known is not a clearance, and known/excluded is the only strong ruling-out move. It also states plainly that the tool never confirms a cause, which is critical behavioral context.

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 description is well-structured with a summary line, bullets, and no wasted words. The final D29 reference is cryptic but does not undermine the overall clarity.

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 three-answer semantics are explained thoroughly, which is essential because there is no output schema. Missing parameter guidance for site and protocol and the absence of explicit sibling routing leave operational gaps at low schema coverage.

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?

With 0% schema description coverage, the description must supply parameter meaning. It clarifies cause as a candidate cause but does not explain site or protocol, both of which appear in the schema with no descriptions.

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 clearly states the tool queries a mounted fault-mechanism library about one candidate cause and enumerates the three possible answers. This distinguishes it from sibling mechanism_library_list, though it uses a noun phrase rather than a direct action verb.

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 establishes when this tool belongs in the workflow: during ranking it can mark a cause known or excluded, but it never confirms a cause. It gives an explicit when-not, though it does not name a specific alternative tool to use for confirmation.

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