Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Read point values

read_points
Read-onlyIdempotent

Read a device's current engineering values and units to check what it is reporting now; specify point names or omit them to read all. Changes nothing; fails if a device or point is missing.

Instructions

Read the current engineering values (after scaling) of a device's points, with their units. Use this to check what a device is reporting right now; use read_registers when you need the raw 16-bit words a Modbus client would receive. Changes nothing. Fails if the device or a named point does not exist.

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": {
      "device_id": "<device_id>"
    },
    "name": "read_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsNoPoint names to read. Omit to read every point of the device.
device_idYesId of a running device, as returned by create_device, clone_device or list_devices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / device_id / description
      Previous value: -"Device id as returned by create_device or list_devices."New value: +"Id of a running device, as returned by create_device, clone_device or list_devices."
    • addedInput schema / properties / points / description
      Added value: +"Point names to read. Omit to read every point of the device."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Changes nothing' is reinforcement rather than new information. The genuinely additive content is the disclosure that scaling is applied and that the call fails when the device or a named point does not exist — error behavior the annotations cannot express. It stops short of covering ordering or what a faulted/disconnected device yields.

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?

Three short sentences with the operation stated first, then the alternative, then the side-effect/error profile. Nothing is padded and every clause carries either routing or behavioral information.

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 two-parameter read tool with no output schema, the definition covers what is returned (scaled values with units), safety, and failure modes, which is enough to invoke it correctly. Minor gaps remain on the shape and ordering of a bulk read when points is omitted, but nothing blocks correct use.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, including that omitting points reads every point of the device. The description only adds the implicit notion that point names are validated (failure if a named point does not exist), which is marginal value over the schema; baseline 3 applies.

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?

States a specific verb and resource ('Read the current engineering values ... of a device's points') plus the distinguishing detail that values are post-scaling and carry units. It explicitly names the sibling read_registers and the dimension on which the two differ (scaled values vs raw 16-bit words), so an agent can discriminate without opening either schema.

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

Usage Guidelines5/5

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

Gives positive guidance ('use this to check what a device is reporting right now') and an explicit alternative with the condition that selects it ('use read_registers when you need the raw 16-bit words a Modbus client would receive'). That is a complete when/when-not routing rule.

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