Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Remove a point from a device

remove_point
Destructive

Delete one named point and any signal on it from a running simulated Modbus device, leaving the device and other points active. Use for point cleanup, not whole-device removal.

Instructions

Delete one named point from a running device, together with any signal on it. Only the definition is removed: the raw value last stored at its address stays readable by Modbus clients until overwritten (or is rejected if the device is strict and no other point covers the address). The device and its other points keep running. Use remove_device to remove the whole device. 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>"
    },
    "name": "remove_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointYesName of an existing point on that device (see get_device or read_points).
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.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, yet the description goes further by disclosing exactly what is destroyed (the definition and its signal) and what survives (the raw register value stays readable by Modbus clients, other points and the device keep running). It also notes the edge case where a strict device rejects the orphaned address, which is genuinely non-obvious behavior.

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, each carrying distinct information: scope, what persists, sibling routing, and failure mode. The most decision-relevant facts (one point vs whole device) are front-loaded and there is no 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?

For a two-parameter destructive tool with no output schema, the description covers what is removed, what remains, how the call fails, and which sibling to use instead. Nothing an agent needs in order to call it safely is missing.

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 device_id and point are already documented in the schema, including cross-references to create_device, list_devices and get_device/read_points. The prose adds no new meaning about the parameters themselves, so the baseline of 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?

The description opens with a specific verb and resource ("Delete one named point from a running device, together with any signal on it") and explicitly names the sibling it is not: remove_device removes the whole device. An agent can distinguish it from remove_device without inspecting 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 Guidelines4/5

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

It states the selecting condition against the nearest alternative ("Use remove_device to remove the whole device") and defines the failure condition ("Fails if the device or point does not exist"). It does not mention other point-level siblings such as add_point, set_point or read_points as adjacent actions, but the when-to-use framing is clear and leaves no ambiguity about scope.

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