Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_psets

Manage property set libraries, definitions, and instances for Trimble Connect model objects. Perform CRUD operations, validate property schemas, handle bulk changesets, and access version history.

Instructions

Trimble Connect Property Set Service (PSet): libraries, definitions, pset instances, policies, changesets. Regional service URI is resolved automatically. In pset paths, 'link' is the FRN of the external resource (e.g. model object). Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • me: GET /me — current user info

  • library_create: POST /libs — body: library definition

  • library_get: GET /libs/{id} — id=libId

  • library_update: PATCH /libs/{id} — id=libId, body: fields to update

  • library_delete: DELETE /libs/{id} — id=libId

  • library_policy_get: GET /libs/{id}/policy — id=libId

  • library_policy_put: PUT /libs/{id}/policy — id=libId, body: access control policy

  • definitions_list: GET /libs/{id}/defs — id=libId, query: {top?, skiptoken?, prefix?}

  • definition_create: POST /libs/{id}/defs — id=libId, body: definition with data schema

  • definition_get: GET /libs/{id}/defs/{subId} — id=libId, subId=defId

  • definition_update: PATCH /libs/{id}/defs/{subId} — id=libId, subId=defId, body: fields to update

  • definition_delete: DELETE /libs/{id}/defs/{subId} — id=libId, subId=defId

  • definition_versions: GET /libs/{id}/defs/{subId}/versions — id=libId, subId=defId

  • definition_version_get: GET /libs/{id}/defs/{subId}/versions/{version} — id=libId, subId=defId, version=version number

  • definition_schema_get: GET /libs/{id}/defs/{subId}/schema/{version} — id=libId, subId=defId, version=schema version

  • definition_validate: POST /libs/{id}/defs/{subId}/validate — id=libId, subId=defId, body: values to validate

  • psets_list_by_definition: GET /libs/{id}/defs/{subId}/psets — id=libId, subId=defId

  • psets_list_for_link: GET /psets/{id} — id=link (FRN), query: {top?, skiptoken?}

  • pset_get: GET /psets/{id}/{subId}/{extraId} — id=link, subId=libId, extraId=defId

  • pset_update: PATCH /psets/{id}/{subId}/{extraId} — id=link, subId=libId, extraId=defId, body: {props}

  • pset_delete: DELETE /psets/{id}/{subId}/{extraId} — id=link, subId=libId, extraId=defId

  • pset_versions: GET /psets/{id}/{subId}/{extraId}/versions — id=link, subId=libId, extraId=defId

  • pset_version_get: GET /psets/{id}/{subId}/{extraId}/versions/{version} — id=link, subId=libId, extraId=defId, version

  • batch_get: POST /batch-get — body: {psets:[{libId, defId, link, v?}]}

  • changeset: POST /psets/changeset — body: changeset (bulk create/update)

  • changeset_async: POST /psets/changeset-async — body: changeset

  • changeset_status: GET /psets/changeset/{id} — id=changesetId

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)
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses automatic regional URI resolution, path placeholder filling, and maps each action to HTTP methods and URL patterns. However, it does not cover error handling, permissions, or rate limits, which would elevate transparency further.

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 long due to the many actions listed, but it is well-organized into a numbered list. It could be trimmed by grouping similar actions or using a table, but the structure is functional.

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?

The description fully covers the mapping from actions to URLs and parameters. However, it does not describe return values or outputs for any action, which is a gap since there is no output schema to compensate.

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 description coverage is 100%, but the description adds significant value by explaining how the 'action' parameter selects endpoints and how parameters fill path placeholders. This goes beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for the Trimble Connect Property Set Service, covering libraries, definitions, pset instances, policies, and changesets. It distinguishes itself from sibling tools by focusing on property set operations, though it could be more specific about its unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent to select an endpoint via the 'action' parameter and lists all actions, but does not provide explicit guidance on when to use this tool versus siblings or when not to use it. The context is implied rather than stated.

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