Skip to main content
Glama

lire_variables

Read-onlyIdempotent

Reads multiple PLC variables in one request so you can retrieve current process or sensor values without separate calls.

Instructions

Lit plusieurs variables en une seule requête à l'automate.

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": {
      "chemins": "<chemins>"
    },
    "name": "lire_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheminsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds only the efficiency framing of a single request; it says nothing about how partial failures are handled (e.g. whether one bad path fails the whole batch) or whether invalid paths are silently dropped, which is the most important behavioral question for a batch read.

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?

One short sentence with no filler, and the batching point is front-loaded. It is efficient but so terse that it reads as a summary rather than a usable definition.

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?

An output schema exists, so return values need not be described, and the tool is structurally simple with one parameter. However, the one parameter is the entire input contract and its format is undocumented in both schema and description, leaving a real gap for an otherwise simple tool.

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% and the single parameter "chemins" is an array of strings whose format is entirely unexplained — no example path syntax, no naming convention, no indication of how many entries are allowed. The description must compensate here and does not, so an agent cannot reliably construct a valid call from the definition alone.

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 gives a specific verb and resource ("Lit ... variables" from the PLC) and adds the batching scope ("plusieurs variables en une seule requête"), which implicitly separates it from the singular sibling lire_variable. It stops short of naming an alternative explicitly, so the differentiation is inferable rather than stated.

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?

"en une seule requête" implies the batch use case — fetch many values in one round trip — but the definition never says when to prefer this over repeated lire_variable calls, nor any preconditions such as the PLC being connected or reachable. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.