Skip to main content
Glama

lire_variable

Read-onlyIdempotent

Reads the current value of an OPC UA PLC variable, returning its unit, timestamp, and quality for live monitoring.

Instructions

Lit la valeur actuelle d'une variable (ex. « Four2.Temperature »), avec unité, horodatage et qualité.

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": {
      "chemin": "<chemin>"
    },
    "name": "lire_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheminYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already carry readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered without prose. The description does add that the response includes unit, timestamp and quality, but an output schema exists, so this is largely duplicating structured data rather than disclosing non-obvious behavior such as refresh latency or behavior when a variable is in bad quality.

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?

A single front-loaded sentence: verb, resource, scope example, and the three returned attributes. No filler and nothing repeated.

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?

For a one-parameter read tool with an output schema, the definition covers purpose, path format and return contents. Missing only edge-case behavior (invalid path, stale/bad quality values) that an agent might need, but the core is sufficient.

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

Parameters4/5

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

Schema description coverage is 0% — the schema only says "Chemin" as a string. The description compensates by giving a concrete path syntax example ("Four2.Temperature"), which tells the agent what format to supply. A 4 rather than 5 because it doesn't state the syntax rules, case sensitivity, or behavior for an unknown path.

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?

States a specific verb ("Lit la valeur actuelle") and a precise resource (a single variable's current value), and the example « Four2.Temperature » makes the singular scope unambiguous, implicitly separating it from the plural sibling lire_variables and the mutation sibling ecrire_variable. It stops short of naming those siblings explicitly.

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?

Usage is only implied: reading a variable's present value is self-evident from the verb, but nothing tells the agent when to prefer lire_variables, historique, or a cached/event-based alternative. No prerequisites or exclusions are given.

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