Skip to main content
Glama
industrial-aiops

OT-AIops

by industrial-aiops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fins_read_words

Read-only

Read 16-bit words from Omron PLC memory areas (DM, CIO, W, H, A, EM) at a given address. Retrieve multiple consecutive words for monitoring or troubleshooting.

Instructions

[READ][risk=low] Read 16-bit words from an Omron memory area (FINS 0101).

Args:
    area: Memory area: "DM", "CIO", "W", "H", "A", or "EM" (current bank).
    address: Word address to start at, e.g. 100 for DM100.
    endpoint: Endpoint name from config.
    count: Number of consecutive words (1..500, capped server-side).

Returns dict: {endpoint, area, address, count, words:[int,...]} (unsigned 16-bit).

Example: fins_read_words(area="DM", address=100, count=8).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNoDM
countNo
addressNo
endpointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only and safe operation. The description adds behavioral detail: server-side capping of count (1..500) and the specific FINS command. It does not contradict 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?

Structured layout with Args, Returns, Example. Every sentence adds value, no redundancy. Front-loaded with purpose and risk level.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers essential information: return format, parameter constraints, server-side cap. Lacks error conditions or handling of invalid inputs, but annotation openWorldHint suggests some flexibility. Sufficient for a read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully explains all four parameters: area (with allowed values), address (example format), endpoint (from config), and count (range). Example reinforces usage.

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 starts with a clear action verb 'Read' and specifies the resource '16-bit words from an Omron memory area', explicitly referencing the FINS 0101 command. This distinguishes it from sibling tools like fins_read_bits and fins_read_many.

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?

No explicit guidance on when to use this tool versus alternatives such as fins_read_bits or fins_read_many. The description implies usage for word-sized data, but lacks when-not or alternative recommendations.

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