Skip to main content
Glama
Industrial-AIops Energy

Industrial-AIops Energy

mechanism_library_list

Read-only

Lists the fault mechanisms mounted for a site and shows where each mechanism came from, so you can verify configured fault sources.

Instructions

[READ][risk=low] The fault mechanisms mounted for a site, and where each came from.

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

Input Schema

NameRequiredDescriptionDefault
siteNodefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

C2.8/5.0
Behavior2/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] tags simply repeat that. The 'where each came from' hint gives some output-context, but the description adds no behavioral detail beyond annotations such as pagination, filtering, or side-effect notes.

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 main sentence is compact and front-loaded with the core meaning. However, the '[READ][risk=low]' prefix is redundant with the annotations and adds noise, preventing a perfect score.

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 simple read-only tool with one optional parameter, this is minimally usable: it communicates the subject and what output to expect at a high level. But without an output schema, it should more clearly describe the return structure and what 'where each came from' means in practice.

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 must compensate for the undocumented 'site' parameter. It only weakly connects to the parameter with the phrase 'for a site', but gives no details about valid values, format, or behavior when omitted.

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 states the resource ('fault mechanisms mounted for a site') and adds the provenance scope ('where each came from'), which is specific enough to understand the tool's purpose. However, it does not explicitly differentiate itself from the sibling mechanism_library_check, so it loses the fifth point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as mechanism_library_check. The phrase 'for a site' implies a contextual use, but no explicit conditions, exclusions, or alternative tools are mentioned.

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