Skip to main content
Glama
ROCTUP

1C Testpilot

by ROCTUP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tc_find

Search the UI tree for objects in 1C:Enterprise test client by name, class, type, or title. Find one or multiple, or wait for display, with timeout and pagination support.

Instructions

Search the UI tree for objects.

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

  • find_object(name=null, cls=null, type=null, root_ref=null, title=null, timeout=0, scope='window') Find the first object matching the criteria (parameters as in tc_find(action="find_objects")). When nothing matched, the answer carries the same filter diagnostics as tc_find(action="find_objects"). (1C 8.3.3+)

  • find_objects(name=null, cls=null, type=null, root_ref=null, title=null, timeout=0, scope='window', limit=null, cursor=null) Search UI objects: name/title support * ?; cls/type use discovered class/platform kind (tc_app(action="get_child_objects")). root_ref defaults to active window; scope=application requires omitting it. timeout retries while no matches (0: once). Empty results are ok; cls/type diagnostics identify unknown filters and list observed kinds. Windows/command buttons include url when available. No limit returns all; limit=1..1000 pages with total/has_more/next_cursor. Continue with cursor alone (plus connection_id if needed), no filters. Pages retain the original result for 5 minutes; elements may become stale. (1C 8.3.3+)

  • wait_for_object_displayed(name=null, cls=null, type=null, title=null, timeout=60) Poll the UI tree until an object matching the criteria appears, up to timeout seconds. Returns the object, or ok=False on timeout. Criteria as in tc_find(action="find_objects"). On timeout the answer says whether a cls was seen at all and lists the classes that were actually present, so a misspelled class name is distinguishable from an object that never appeared. (1C 8.3.3+) root_ref selects the client; otherwise set connection_id when several clients are connected. Use tc_session(action="list_connections"). Success may omit target/connection echoes and shorten window details. Use returned references unchanged in root_ref; re-find expired elements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clsNo
nameNo
typeNo
limitNo
scopeNo
titleNo
actionYes
cursorNo
timeoutNo
root_refNo
connection_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "default": null,
+  "title": "Cursor",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": null,
+  "title": "Limit",
+  "type": "integer"
+}
  2. Changed1 schema field changedv1.5.0
    • addedInput schema / properties / scope
      Added value: +{
+  "default": null,
+  "enum": [
+    "window",
+    "application"
+  ],
+  "title": "Scope",
+  "type": "string"
+}
  3. First observedv1.0.0

TDQS

A4.8/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 well: timeout retry semantics (0: once), empty-result behavior, pagination retention window (pages kept 5 minutes, elements may go stale), and that success may omit target/connection echoes. It also explains the diagnostic payload on cls/type misses and on wait timeouts.

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 one-line summary followed by clean per-action bullets, so structure is strong. It is somewhat long and repetitive (the "(1C 8.3.3+)" markers and repeated "Criteria as in tc_find(action='find_objects')" add bulk without information).

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 3-action, 11-parameter tool with no annotations and no output schema, the description covers filters, paging, staleness, and key return fields (total/has_more/next_cursor, ok=False). A few return details (full object payload shape) remain implicit, but the essentials for correct invocation are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 effectively documents all 11 parameters: wildcard support on name/title, cls/type as discovered kinds, root_ref default to active window and reuse-unchanged guidance, scope enum behavior, limit paging range 1..1000, cursor continuation, connection_id disambiguation, and timeout retry semantics.

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 ("Search the UI tree for objects") and then enumerates the three distinct actions with their individual semantics. The sibling tools (tc_table, tc_session, tc_app, etc.) are unrelated domains, so no sibling overlap ambiguity remains; an agent can tell exactly what this tool searches.

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?

Explicitly routes between actions: find_object returns the first match, find_objects pages results, wait_for_object_displayed polls. It also states the required-action convention ("Pass action=name and only that action's parameters"), cursor continuation rules, and that scope=application requires omitting root_ref.

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