Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_views

Manage 3D views in Trimble Connect: create, read, update, delete views, camera, presentation, section boxes, section planes, and markups.

Instructions

Trimble Connect 3D Views: CRUD plus camera, presentation, section box/planes and markups. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • list: GET /views — query: {projectId}

  • get: GET /views/{id} — id=viewId

  • create: POST /views — body: view definition {name, projectId, models?, camera?...}

  • update: PATCH /views/{id} — id=viewId, body: fields to update

  • delete: DELETE /views/{id} — id=viewId

  • camera_get: GET /views/{id}/camera — id=viewId

  • camera_update: PATCH /views/{id}/camera — id=viewId, body: camera

  • presentation_get: GET /views/{id}/presentation — id=viewId

  • presentation_update: PATCH /views/{id}/presentation — id=viewId, body: presentation

  • sectionbox_get: GET /views/{id}/sectionbox — id=viewId

  • sectionbox_update: PUT /views/{id}/sectionbox — id=viewId, body: section box

  • sectionbox_delete: DELETE /views/{id}/sectionbox — id=viewId

  • sectionplanes_list: GET /views/{id}/sectionplanes — id=viewId

  • sectionplane_create: POST /views/{id}/sectionplanes — id=viewId, body: section plane

  • sectionplane_update: PATCH /views/{id}/sectionplanes — id=viewId, body: section plane

  • sectionplane_delete: DELETE /views/{id}/sectionplanes/{subId} — id=viewId, subId=sectionplaneId

  • markups_list: GET /views/{id}/markups — id=viewId

  • markups_create: POST /views/{id}/markups — id=viewId, body: markups

  • markups_update: PATCH /views/{id}/markups — id=viewId, body: markups

  • markup_delete: DELETE /views/{id}/markups/{subId} — id=viewId, subId=markupId

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

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

No annotations are provided, so the description carries full behavioral disclosure burden. It details HTTP methods (GET, POST, PATCH, DELETE) for each action, which implies mutability for some actions, but does not explicitly state if operations are destructive, require authentication, or have side effects. The description is adequate but lacks explicit warnings.

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 description is long due to the number of actions but is well-structured with a bullet list grouping actions by sub-resource. The purpose is front-loaded, and each action entry is concise. Some redundancy exists (e.g., repeated path patterns), but overall it balances detail and structure.

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?

Given the tool's complexity (20 actions, 10 parameters, no output schema), the description is fairly complete. It covers all actions, parameter relationships, and body suggestions. Missing return value details or error handling, but sufficient for selecting and invoking actions.

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% with good descriptions. The tool description adds value by mapping actions to required parameters (e.g., id=viewId for get, body for create) and explaining how path placeholders fill parameters. This provides practical context beyond the schema alone.

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 clearly states the tool handles CRUD operations on Trimble Connect 3D Views, including camera, presentation, section box/planes, and markups. It lists all 20 actions and explains how to select endpoints via the action parameter. This distinguishes it from siblings like tc_list_views (which likely only lists views).

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 explains how to use the action parameter and path placeholders, but does not provide explicit guidance on when to use this tool versus more specific sibling tools (e.g., tc_list_views for listing views). It implies this is the single tool for all view operations, but lacks when-not-to-use or alternative suggestions.

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