Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_files

Manage Trimble Connect files: retrieve details, versions, download URLs; check in/out, manage permissions, alignment, exports, and uploads.

Instructions

Trimble Connect Files: details, versions, download URL, check-in/out, permissions, alignment, exports, upload orchestration (JSON steps only). Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • get: GET /files/{id} — id=fileId

  • update: PATCH /files/{id} — id=fileId, body: {name?, parentId?...}

  • delete: DELETE /files/{id} — id=fileId

  • versions: GET /files/{id}/versions — id=fileId

  • versions_v21: GET /2.1/projects/{projectId}/files/{id}/versions — id=fileId (paged v2.1 API)

  • processing_status: GET /files/{id}/status — id=fileId

  • process: POST /files/{id}/process — id=fileId, body: {format:'TRB', versionId?} — trigger model assimilation/processing

  • download_url: GET /files/fs/{id}/downloadurl — id=fileId, query: {versionId?}

  • checkin: POST /files/{id}/checkin — id=fileId

  • checkout: POST /files/{id}/checkout — id=fileId

  • permissions_get: GET /files/{id}/permissions — id=fileId

  • permissions_update: PATCH /files/{id}/permissions — id=fileId, body: permissions

  • supported_formats: GET /files/formats — list supported 2D/3D/spatial formats

  • snapshot: GET /files/fs/snapshot — query: {projectId} — active file/folder snapshot

  • create_export: POST /files/export — body: export request

  • get_export: GET /files/export/{id} — id=exportId

  • initiate_upload: POST /files/fs/initiate — body: upload init request (returns signed upload URLs)

  • initiate_package_upload: POST /files/fs/upload — body: package upload request

  • complete_multipart_upload: POST /files/fs/upload/{id}/complete — id=uploadId, body: parts

  • commit_upload: POST /files/fs/commit — body: commit request

  • upload_details: GET /files/fs/upload — query: upload details params

  • upload_status: GET /files/fs/uploadstatus — query: {uploadId...}

  • alignment_get: GET /files/{id}/alignment — id=fileId

  • alignment_set: PUT /files/{id}/alignment — id=fileId, body: alignment

  • alignment_set_matrix: POST /files/{id}/alignment/matrix — id=fileId, body: matrix

  • alignment_delete: DELETE /files/{id}/alignment — id=fileId

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPrimary resource ID — required when the action path contains {id}
bodyNoJSON request body for POST/PUT/PATCH (and some DELETE) actions
queryNoQuery parameters as key-value pairs
subIdNoSecondary resource ID — required when the action path contains {subId}
actionYesEndpoint to call (see tool description)
regionYesTrimble Connect region: us (North America), eu (Europe), ap (Asia-Pacific), ap-au (Australia)
extraIdNoTertiary resource ID — required when the action path contains {extraId}
versionNoVersion number — required when the action path contains {version}
projectIdNoProject ID — required when the action path contains {projectId}
bcfVersionNoBCF API version for BCF actions (default 2.1)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose side effects (e.g., mutation actions like delete, checkin, checkout, process), required permissions, rate limits, or error states. For a tool with many write operations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very long but well-structured with a list of actions. The initial sentence is dense and could be clearer. While comprehensive, it is not concise; it could be trimmed by focusing on the action selection pattern.

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

Completeness3/5

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

Given the complexity (10 parameters, numerous actions, no output schema), the description covers all endpoints and parameter mappings. However, it lacks behavioral context (permissions, error handling) and does not explain return values, which would aid an agent in selecting and invoking correctly.

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 100%, so baseline is 3. The description adds significant value by mapping actions to specific paths, showing which parameters are needed for each action, and providing body examples for POST/PUT/PATCH actions (e.g., format:'TRB' for process, request bodies for alignment).

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?

Clearly states it is for Trimble Connect Files and lists all possible actions with specific HTTP methods and paths. The description distinguishes itself from simpler sibling tools like tc_get_file by offering a unified interface for many file operations.

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?

The description explains how to select endpoints via the 'action' parameter and how path placeholders map to input parameters. It provides detailed action examples but does not explicitly guide when to use this tool vs. alternatives like tc_get_file or tc_files_app.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SimonTrim/trb-mcp-server-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server