Skip to main content
Glama
Sign In
plctap

plctap

by ymxc152
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Proxy Frames

get_proxy_frames
Read-onlyIdempotent

Retrieve recent bidirectional transparent proxy frames between host and PLC. Returns latest entries (c2s and s2c), up to 1000 in ring buffer, with adjustable limit.

Instructions

取代理录制的双向透传帧 (direction: c2s=上位机→PLC, s2c=PLC→上位机)。

取最新 limit 条; 环形缓冲硬上限 1000 条 (limit 超限自动截到缓冲 大小, limit<=0 返回空)。

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": {
      "port": "<port>"
    },
    "name": "get_proxy_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.1
    • changedOutput schema / properties / result / items / additionalProperties
      Previous value: -trueNew value: +false
    • addedOutput schema / properties / result / items / description
      Added value: +"get_listener_frames / get_proxy_frames 共用的单帧记录。"
    • addedOutput schema / properties / result / items / properties
      Added value: +{
+  "direction": {
+    "type": "string"
+  },
+  "frame_hex": {
+    "type": "string"
+  },
+  "peer": {
+    "type": "string"
+  },
+  "ts": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / result / items / required
      Added value: +[
+  "ts",
+  "direction",
+  "peer",
+  "frame_hex"
+]
  2. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses meaningful behavior: the ring buffer hard cap of 1000, automatic truncation of limit, and empty result for limit<=0. These are concrete runtime behaviors that annotations do not convey.

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 compact and every sentence carries useful information: the data source, direction meaning, and limit/buffer semantics. No filler or repetition of schema types.

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

Completeness3/5

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

The description covers limit and buffer semantics wellwing and an output schema exists, so return structure is likely handled elsewhere. But the required port parameter is undocumented, and there is no statement about ordering or behavior when no frames have been recorded. These are modest gaps for an otherwise simple read tool.

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?

With 0% schema description coverage, the description must compensate, and it does for limit: latest N frames, truncation at buffer cap, non-positive returns empty. However, the required port parameter is left entirely unexplained in both schema and description, which is a notable gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: fetch proxy-recorded bidirectional passthrough frames, with direction conventions c2s and s2c. It is clearly distinguishable from sibling get_listener_frames by the explicit 'proxy-recorded' scope, though it does not name that alternative directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The tool's context is implied: it is for reading frames captured by the proxy, after proxy operation. However, it gives no explicit guidance on when to prefer this over get_listener_frames or other sibling tools, and no when-not-to-use conditions.

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

Deploy Server

Other Tools