Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Make a point change over time

set_signal
Idempotent

Attach sine, ramp, random, counter, or square signals to a device point so its value changes over time, replacing any existing signal. Use it to simulate dynamic values in a Modbus device for testing.

Instructions

Attach a signal to one point so its value changes by itself: sine, ramp, random, random walk, counter, square or constant. It replaces any signal already on that point and runs until replaced, stopped, or overwritten by set_point. Pass signal null to stop the signal and keep the current value. Use set_point for a fixed value and apply_scenario to change several things on a timeline. Returns the point with its current value.

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>",
      "signal": "<signal>"
    },
    "name": "set_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointYesName of an existing point on that device (see get_device or read_points).
signalYesSignal object. One of: {"type":"constant","value":N} | {"type":"ramp","from":N,"to":N,"period_s":N,"repeat":true} | {"type":"sine","min":N,"max":N,"period_s":N} | {"type":"random","min":N,"max":N} | {"type":"random_walk","min":N,"max":N,"step":N} | {"type":"counter","per_second":N,"rollover":N (optional)} | {"type":"square","low":N,"high":N,"period_s":N}. Values are engineering values (after scaling).
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 / point / description
      Added value: +"Name of an existing point on that device (see get_device or read_points)."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false. The description adds genuine behavior beyond them: it replaces any existing signal on the point, persists until replaced/stopped/overwritten by set_point, and returns the point with its current value. Minor tension with destructiveHint=false, since replacing an existing signal does overwrite prior configuration, though it is scoped replacement rather than data loss.

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 tight sentences, each doing a distinct job: purpose, lifecycle, stop semantics, and sibling routing. The capability list is front-loaded and nothing is redundant.

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?

No output schema exists, but the description states what is returned ('the point with its current value'), and lifecycle, replacement, and stop behavior are all covered for a three-required-parameter tool. An agent has enough to call it correctly and know the side effects.

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 the baseline is 3, but the description adds meaning the schema does not: passing signal null stops the signal while retaining the current value. It also frames the signal as a point-level attachment rather than a standalone object, which clarifies how the parameter is consumed.

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 ('Attach a signal to one point so its value changes by itself') and enumerates the supported signal kinds, so the agent knows exactly what this does. The final sentences distinguish it from set_point (fixed value) and apply_scenario (multiple things on a timeline).

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 explicit routing: use set_point for a fixed value, use apply_scenario to change several things on a timeline. It also states the stop condition ('Pass signal null to stop the signal and keep the current value'), which is a real when-to-use rule, not just a hint.

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