Skip to main content
Glama
ROCTUP

1C Testpilot

by ROCTUP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tc_scenario

Record and replay 1C UI action scenarios to automate testing and reproduce user workflows.

Instructions

Record and replay UI scenarios.

  • marks a required action parameter; the group schema treats action parameters as optional. Pass action="name" and only that action's parameters. Actions:

  • record_cancel() Cancel user-actions recording (discard the scenario). (1C 8.3.2+)

  • record_finish(path=null) Stop recording; return XML in uilog or save path (relative to SERVER working directory; returns absolute). Write failure returns ok=false/error/path AND uilog; recording already stopped, so retry cannot recover it. Synth completion failure returns finish_not_confirmed with preserved XML. lost_actions means incomplete replay. no_effect lists unchanged readbacks by CALL index, not XML step; not proof of no effect. observed/not_observed count successful/unavailable readbacks; readback/scope describe coverage. Empty no_effect with observed=0 means nothing checked. (1C 8.3.2+)

  • record_pause() Pause user-actions recording: actions performed until tc_scenario(action="record_resume") stay out of the scenario. (1C 8.3.2+)

  • record_resume() Resume user-actions recording. (1C 8.3.2+)

  • record_start() Start recording a scenario (uilog) that tc_scenario(action="run_scenario") can replay later. Perform the real, effect-producing actions between start and tc_scenario(action="record_finish"), then read the scenario from finish. (1C 8.3.2+)

  • run_scenario(uilog=null, path=null, result_mode='summary') Replay uilog XML or path on the current form. Unsupported steps are skipped/listed; first failure stops at 0-based stopped_at. total counts reported steps, played counts attempted steps including failures. ok means all attempted commands accepted, not all effects verified; full steps[].changed follows each action's contract. Default summary; result_mode=full adds steps. Logs retain full details in both modes. Set connection_id when several clients are connected. Use tc_session(action="list_connections"). Success may omit target/connection echoes and shorten window details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
uilogNo
actionYes
result_modeNo
connection_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.0
    • addedInput schema / properties / result_mode
      Added value: +{
+  "default": null,
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "title": "Result Mode",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and delivers: error semantics (ok=false/error/path), unrecoverable write failure after recording already stopped, finish_not_confirmed XML preservation, lost_actions meaning, no_effect scope caveats, observed/not_observed counting, and that ok means commands accepted rather than effects verified. This is unusually rich disclosure.

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 purpose followed by a scannable per-action bullet list; nearly every sentence conveys constraints or semantics. It is long, but the density is justified by six actions with distinct contracts, with only minor repetition between the header note and the bullet bodies.

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 six-action mutation/replay tool with no annotations and no output schema, the description supplies action contracts, error and partial-failure behavior, result_mode semantics, and a cross-client connection note. Nothing essential to correct invocation appears 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 coverage is 0%, so the description must compensate, and it largely does: path is relative to the SERVER working directory and returned absolute, uilog carries XML or a path for run_scenario, result_mode summary vs full is explained, and connection_id is tied to multi-client sessions. Only path/uilog format syntax is left thin.

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+resource ('Record and replay UI scenarios') and then enumerates six sub-actions, each with its own specific purpose. An agent can distinguish record_* from run_scenario and from sibling tools like tc_form/tc_window without opening a 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?

Gives explicit sequencing (perform real actions between record_start and record_finish, then read from finish; replay via run_scenario) and cross-references tc_session for connection_id. It does not state any when-not-to-use condition, but usage context is clear.

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