Skip to main content
Glama
Sign In
twincat-mcp

twincat-mcp

by Disectron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rec_delete

Destructive

Stops a running recording, deletes the recording and its exports from disk, and logs size and SHA-256 for audit. Requires confirmation in guarded mode.

Instructions

Stop (if running) and delete a recording and its exports from disk. Destructive-class (field report R11): a recording is evidence — guarded mode needs tc_request_confirmation(action='rec_delete', target=); the audit keeps the deleted file's size and SHA-256 so its content stays identifiable.

Input Schema

NameRequiredDescriptionDefault
idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.12
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confirm Token"
+}
  2. First observedv0.6.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds rich context beyond them: that it stops a running recording first, that exports are also removed, the confirmation gate required in guarded mode, and that the audit retains size and SHA-256 for identifiability. That is genuine behavioral disclosure an agent needs.

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?

Front-loaded with the action, then the destructive-class and confirmation detail. Every clause adds material information; it is a bit dense but not padded.

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

Completeness4/5

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

For a destructive mutation tool with an output schema present, the description covers scope, side effects, confirmation requirement, and audit retention. The only shortfall is that neither the description nor the schema explains the confirm_token parameter.

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 0%, so the description must carry parameter meaning. It references the id (via target=<id>) and the confirmation flow, which maps to confirm_token, but never names or explains confirm_token directly nor its format. Partial compensation leaves a gap.

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?

States a specific verb (delete) and resource (a recording and its exports on disk), plus the side behavior 'stop (if running)'. This clearly distinguishes it from the sibling rec_stop, which only halts a recording. An agent can select it without opening the 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 specifies the guarded-mode prerequisite explicitly: tc_request_confirmation(action='rec_delete', target=<id>). This gives a clear when-to-use workflow, though it doesn't state when NOT to use it versus alternatives like rec_stop or rec_profile_delete.

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