Skip to main content
Glama
ROCTUP

1C Testpilot

by ROCTUP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tc_session

Connect to, launch, or stop a 1C test client over its network protocol, and list or disconnect active connections.

Instructions

Connect to, launch or stop the 1C test client. In the signatures below a trailing * marks a REQUIRED parameter — the group schema itself accepts every parameter as optional. Actions:

  • connect(port*, host='127.0.0.1', version=null) Connect to a running 1C test client (started with /TESTCLIENT -TPort ). version is the platform version (e.g. '8.5.1.1343') and MUST match the running platform, else the handshake fails; if omitted a built-in default is used. Call this before any other tc_* tool. A different host/port creates another connection. The same host/port reconnects that client; its connection_id is retained, but find elements again before using them.

  • disconnect() Close the connection to the test client.

  • launch_client(base*, port=null, server=False, user=null, password=null, version=null, exe=null, extra_args=null, wait=30, connect=True) Launch a 1C test client and wait until it accepts connections on port, then optionally connect to it. base is a file infobase path (default), or 'server\infobase' when server=True. user/password — infobase credentials (optional; the password is passed on the command line and is visible in the OS process list). exe — full path to 1cv8.exe on Windows, or 1cv8/1cv8c on Linux (else env TC1C_PLATFORM_EXE or standard install path). Only the 1C platform executable is launched. Omit port to allocate a free local port. Each launch creates a separate connection_id. Linux requires access to a graphical session via the server's DISPLAY/XAUTHORITY environment. With connect=false ok means only that the port answers — the client can be up and showing an error, so check it before relying on it.

  • list_connections() List registered clients with connection_id, host, port, base, user and recording status. base/user are known for clients launched here; listing does not probe client health.

  • stop_client() Stop the test client started by launch_client in this connection, and disconnect from it. Unsaved changes may be lost. If stopping fails, retain the process so the call can be retried. connection_id selects the client. With several clients, connection_id is required. Use tc_session(action="list_connections").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exeNo
baseNo
hostNo
portNo
userNo
waitNo
actionYes
serverNo
connectNo
versionNo
passwordNo
extra_argsNo
connection_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/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 burden and does so richly: the password is visible in the OS process list, stop_client may lose unsaved changes yet retains the process on failure for retry, version must match or the handshake fails, Linux needs DISPLAY/XAUTHORITY, and connect=false only proves the port answers. These are non-obvious operational traits an agent could not infer from the schema.

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 purpose is front-loaded followed by clearly delimited per-action blocks with required-parameter markers, which is the right structure for a 13-parameter multi-action tool. It is necessarily long, though a few lines (e.g. duplicating the default-port note) could be trimmed.

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 complex five-action connection manager with no annotations and no output schema, the description covers launch, connect, teardown, and failure semantics thoroughly. The residual gaps are the undocumented extra_args/wait parameters and the absence of any indication of what these calls return.

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 does for most parameters — base/server path semantics, exe resolution order and platform defaults, version matching, and connection_id selection are all explained. Gaps remain for extra_args and wait (listed but not described), which are the only parameters lacking meaning beyond their names.

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 states a specific verb+resource ('Connect to, launch or stop the 1C test client') and disambiguates from siblings by mandating it be called before any other tc_* tool. The per-action breakdown (connect/disconnect/launch_client/list_connections/stop_client) lets an agent tell exactly which entry point to use.

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 gives explicit ordering ('Call this before any other tc_* tool'), routing ('Use tc_session(action="list_connections")'), and conditions ('With several clients, connection_id is required'). It also explains lifecycle rules such as a different host/port creating another connection and the same host/port reconnecting and retaining connection_id.

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