Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Set a point to a fixed value

set_point
Idempotent

Sets a simulator point to a fixed engineering value and stops any signal on that point so the value persists until changed; returns the updated point.

Instructions

Set one point to a fixed engineering value (the simulator applies the point's scale and data type). Any signal running on that point is stopped, so the value stays until changed again. Use set_signal for a value that changes over time and write_registers to write raw words at an address. Returns the point with its new value. Fails if the device or 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>",
      "point": "<point>",
      "value": "<value>"
    },
    "name": "set_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointYesName of an existing point on that device (see get_device or read_points).
valueYesNew engineering value. For bool points use 0 or 1.
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. Changed3 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 / point / description
      Added value: +"Name of an existing point on that device (see get_device or read_points)."
    • addedInput schema / properties / value / description
      Added value: +"New engineering value. For bool points use 0 or 1."
  2. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare write, idempotent and non-destructive hints, but the description adds real behavioral context the annotations cannot: the simulator applies the point's scale and data type, any signal running on the point is stopped so the value persists, the call returns the point with its new value, and it fails if the device or point is missing. The stopped-signal side effect is a notable side effect not captured by destructiveHint=false, but it is disclosed rather than contradicted.

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?

Four short sentences, front-loaded with the core action, then side effect, then sibling routing, then failure mode. No sentence is filler.

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

Completeness5/5

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

With no output schema, the description states what is returned (the point with its new value) and the failure condition. Combined with full schema coverage and annotations, an agent has everything needed to call it correctly.

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 coverage is 100%, so all three parameters are documented, giving a baseline of 3. The description adds marginal meaning beyond the schema by explaining that the value is an engineering value subject to the point's scale and data type, and by restating the existence prerequisite for device and point.

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?

Names a specific verb and resource ('Set one point to a fixed engineering value') and immediately distinguishes the tool from set_signal and write_registers. An agent can tell exactly what this does and what it is not without opening any 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?

Explicitly routes the agent: use this for a value that stays fixed, use set_signal for a value that changes over time, and use write_registers for raw words at an address. That covers both the sibling alternatives and the condition that selects each.

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