tc_clashes
Manage clash sets in Trimble Connect: create, list, get, update, and delete clash reports to resolve model conflicts.
Instructions
Trimble Connect Clash sets (create, inspect, update, delete clash reports). Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:
list: GET /clashsets — query: {projectId}
get: GET /clashsets/{id} — id=clashId
list_items: GET /clashsets/{id}/items — id=clashId
create: POST /clashsets — body: CreateClashRequest {name, projectId, models, clearance...}
update: PATCH /clashsets/{id} — id=clashId, body: fields to update
delete: DELETE /clashsets/{id} — id=clashId
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Primary resource ID — required when the action path contains {id} | |
| body | No | JSON request body for POST/PUT/PATCH (and some DELETE) actions | |
| query | No | Query parameters as key-value pairs | |
| subId | No | Secondary resource ID — required when the action path contains {subId} | |
| action | Yes | Endpoint to call (see tool description) | |
| region | Yes | Trimble Connect region: us (North America), eu (Europe), ap (Asia-Pacific), ap-au (Australia) | |
| extraId | No | Tertiary resource ID — required when the action path contains {extraId} | |
| version | No | Version number — required when the action path contains {version} | |
| projectId | No | Project ID — required when the action path contains {projectId} | |
| bcfVersion | No | BCF API version for BCF actions (default 2.1) |