Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Show recent Modbus requests

get_traffic_log
Read-onlyIdempotent

Retrieves the most recent Modbus requests a simulated device received, showing function code, address, quantity and reply. Use it to see what client software is polling or confirm a fault took effect.

Instructions

Show the most recent Modbus requests a device received from client software, oldest first: function code, address, quantity and how it was answered, plus the total number of requests served. Use it to see what the software under test is polling or to confirm a fault took effect. The log keeps the last 500 requests per device and is lost when the device is removed. Changes nothing.

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_traffic_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the latest requests to return. Default 50.
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."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 50."New value: +"How many of the latest requests to return. Default 50."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds retention detail not in the schema: the log keeps the last 500 requests per device and is lost when the device is removed, plus the ordering (oldest first) and that a total-served count is included. Those are exactly the operational facts an agent needs before relying on the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scope and returned fields lead, followed by use cases and retention limits – well front-loaded and free of padding. The closing "Changes nothing." restates what readOnlyHint/destructiveHint already declare, a small redundancy.

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 read tool, the definition covers scope, return contents, ordering, buffer capacity, and data-loss conditions. With no output schema present, the enumerated fields substitute adequately, leaving nothing material an agent would need before calling it.

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 device_id's provenance and limit's 1-500 range with a default of 50. The description adds only the ordering context ("most recent ... oldest first"), which clarifies how limit behaves but goes no further; 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?

Names a specific verb and resource ("Show the most recent Modbus requests a device received from client software") and then enumerates the returned fields (function code, address, quantity, response, total count), which clearly separates it from value-reading siblings like read_registers or read_points.

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?

Gives two concrete use cases: observing what the software under test is polling, and confirming a fault took effect. It does not explicitly exclude or name an alternative tool, so the routing is clear but not fully disambiguated.

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