Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_bcf

Manage BCF topics, comments, viewpoints, and document references within Trimble Connect projects. Perform CRUD and batch operations via a single endpoint.

Instructions

Trimble Connect BCF/Topic API (default 2.1, set bcfVersion='3.0' for BCF 3.0): topics, comments, viewpoints, extensions, document references, batch operations. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • list_projects: GET /projects

  • get_project: GET /projects/{projectId}

  • extensions_get: GET /projects/{projectId}/extensions — topic types, statuses, priorities, labels, users

  • extensions_update: PUT /projects/{projectId}/extensions — body: extensions

  • default_extensions: GET /projects/{projectId}/defaultextensions

  • topics_list: GET /projects/{projectId}/topics — query: OData filters supported ($filter, $orderby...)

  • topic_get: GET /projects/{projectId}/topics/{id} — id=topicId (guid)

  • topic_create: POST /projects/{projectId}/topics — body: {title, description?, topic_type?, priority?, assigned_to?, topic_status?...}

  • topic_update: PUT /projects/{projectId}/topics/{id} — id=topicId, body: full topic object

  • topic_delete: DELETE /projects/{projectId}/topics/{id} — id=topicId

  • topics_batch_create: POST /projects/{projectId}/topics/batch — body: array of topics

  • topics_batch_update: PATCH /projects/{projectId}/topics/batch — body: array of topic patches

  • comments_list: GET /projects/{projectId}/topics/{id}/comments — id=topicId

  • comment_get: GET /projects/{projectId}/topics/{id}/comments/{subId} — id=topicId, subId=commentId

  • comment_create: POST /projects/{projectId}/topics/{id}/comments — id=topicId, body: {comment}

  • comment_update: PUT /projects/{projectId}/topics/{id}/comments/{subId} — id=topicId, subId=commentId, body: {comment}

  • comment_delete: DELETE /projects/{projectId}/topics/{id}/comments/{subId} — id=topicId, subId=commentId

  • comments_batch_create: POST /projects/{projectId}/comments/batch — body: array of comments

  • comments_batch_update: PATCH /projects/{projectId}/comments/batch — body: array of comment patches

  • viewpoints_list: GET /projects/{projectId}/topics/{id}/viewpoints — id=topicId

  • viewpoint_get: GET /projects/{projectId}/topics/{id}/viewpoints/{subId} — id=topicId, subId=viewpointId

  • viewpoint_create: POST /projects/{projectId}/topics/{id}/viewpoints — id=topicId, body: viewpoint (camera, snapshot base64...)

  • viewpoint_delete: DELETE /projects/{projectId}/topics/{id}/viewpoints/{subId} — id=topicId, subId=viewpointId

  • viewpoint_selection: GET /projects/{projectId}/topics/{id}/viewpoints/{subId}/selection — id=topicId, subId=viewpointId

  • viewpoint_coloring: GET /projects/{projectId}/topics/{id}/viewpoints/{subId}/coloring — id=topicId, subId=viewpointId

  • viewpoint_visibility: GET /projects/{projectId}/topics/{id}/viewpoints/{subId}/visibility — id=topicId, subId=viewpointId

  • related_topics_get: GET /projects/{projectId}/topics/{id}/related_topics — id=topicId

  • related_topics_update: PUT /projects/{projectId}/topics/{id}/related_topics — id=topicId, body: related topics

  • topic_files_get: GET /projects/{projectId}/topics/{id}/files — id=topicId

  • topic_files_update: PUT /projects/{projectId}/topics/{id}/files — id=topicId, body: file references

  • document_references_list: GET /projects/{projectId}/topics/{id}/document_references — id=topicId

  • document_reference_create: POST /projects/{projectId}/topics/{id}/document_references — id=topicId, body: document reference

  • document_reference_update: PUT /projects/{projectId}/topics/{id}/document_references/{subId} — id=topicId, subId=documentReferenceId, body

  • document_reference_delete: DELETE /projects/{projectId}/topics/{id}/document_references/{subId} — id=topicId, subId=documentReferenceId

  • documents_list: GET /projects/{projectId}/documents

  • document_get: GET /projects/{projectId}/documents/{id} — id=documentId

  • objects: GET /projects/{projectId}/objects

  • changes: GET /projects/{projectId}/changes — query: change tracking params

  • current_user: GET /current-user

  • bcf_versions: GET /bcf/versions — supported BCF versions

  • foundation_versions: GET /foundation/versions

  • foundation_auth: GET /foundation/1.0/auth

  • foundation_current_user: GET /foundation/1.0/current-user

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 must carry full burden. It lists actions but does not disclose behavioral traits such as side effects, required permissions, rate limits, or whether operations are destructive. For instance, 'topic_delete' is listed without any warning about irreversible deletion. The description is purely functional.

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

Conciseness2/5

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

The description is extremely long (over 50 lines) with a massive bulleted list of 44 actions. While it front-loads BCF version and path placeholder info, the bulk is a wall of text that is hard to scan. It would benefit from grouping by resource or using tables. Not concise.

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 tool's complexity (10 parameters, 44 actions, no output schema), the description lists all actions and their parameters, which is complete in terms of action coverage. However, it lacks explanation of return values, error handling, or authentication. The absence of output schema is not compensated by description details on response structure. Adequate but with clear gaps.

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 value by explaining how path placeholders ({id}, {subId}, etc.) are filled from parameters and by providing endpoint details (HTTP method, path, and body requirements for many actions). For example, 'topic_create' notes body fields like title, description, topic_type, etc. 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 it is the Trimble Connect BCF/Topic API and lists over 40 actions covering topics, comments, viewpoints, etc. It specifies verb+resource for each action (e.g., 'topics_list: GET /projects/{projectId}/topics'). However, it does not differentiate from sibling tools like tc_bcf_list_topics or tc_bcf_create_topic, which appear to be more specific wrappers.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool vs. alternatives. Given sibling tools like tc_bcf_list_topics and tc_bcf_create_topic, there is no explanation of trade-offs or when to prefer the generic tc_bcf over the more specific ones. No 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