Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Show one device in full

get_device
Read-onlyIdempotent

Retrieve full details for one simulated Modbus device—connection settings, faults, scenario progress, and point addresses, types, and values—when you need complete context instead of values alone.

Instructions

Return everything about one device: connection details, settings, active fault, scenario progress and every point with its address, data type and current value. Use read_points instead when you only need values. Changes nothing. Fails if the id is unknown.

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": "get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field 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."
  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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is largely covered. The description adds useful behavior beyond annotations by stating that unknown device ids cause failure and by describing the return payload scope. It does not cover authentication, rate limits, or error shape, but those are less critical for a read-only single-resource getter.

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?

The description is front-loaded with the primary purpose and return contents. Every sentence earns its place: the alternative routing sentence and the failure sentence both add actionable information. There is no redundant or filler wording.

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 one required parameter, high schema coverage, and no output schema, the description appropriately explains both what is returned and what can go wrong. It also routes the agent to the right sibling when full details are not needed. Nothing essential for correct invocation is missing.

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 100%, so the baseline would be 3. The description still adds meaning by noting that the device_id must refer to a known id and that an unknown id fails, which supplements the schema's description of where ids come from. It does not add format syntax beyond the schema, but the validity constraint is useful.

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 uses a specific verb and resource: it returns full details for one device. It enumerates the returned contents (connection details, settings, active fault, scenario progress, points with address/data type/current value), making the scope concrete. It also distinguishes itself from read_points, so an agent can choose between them without opening schemas.

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?

It explicitly states when to use this tool: when you need everything about one device. It also names the alternative, read_points, and gives the condition that selects it: when you only need values. This is clear routing guidance with an explicit alternative.

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