Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_shares

List, get, create, update, and delete shares to share files and views with external users in Trimble Connect.

Instructions

Trimble Connect Shares (share files/views with external users). Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

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

  • get: GET /shares/{id} — id=shareId

  • get_by_token: GET /shares/token/{id} — id=share token (stoken)

  • create: POST /shares — body: ShareObjectRequest

  • update: PATCH /shares/{id} — id=shareId, body: fields to update

  • delete: DELETE /shares/{id} — id=shareId

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?

No annotations are provided, so the description carries the full burden. It discloses all actions, their HTTP methods, path placeholders, and which parameters are required per action. It implies that create requires a body, update patches fields, etc. It does not mention authentication or rate limits, but the behavioral traits are well covered for a sharing tool.

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 moderately long but well-structured: a brief purpose statement, then a bulleted list of actions. Every sentence is informative. It could be slightly more concise by grouping common patterns, but overall it's efficient and easy to scan.

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 10 parameters and 6 actions, the description covers the essential: how to select actions and map parameters to paths. It doesn't describe response format or error conditions, but with no output schema, that's acceptable. It provides enough context for an AI agent to invoke the tool 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?

The input schema has 100% description coverage, so baseline is 3. The description adds significant value by mapping parameters to path placeholders (e.g., id=shareId, subId, extraId, version) and specifying which action uses which. For example, 'get_by_token' uses 'id' as share token. This clarifies parameter roles beyond the schema.

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 is for sharing files/views with external users via Trimble Connect. It lists specific actions (list, get, create, etc.) that distinguish it from sibling tools like tc_files, tc_folders, etc. The verb 'share' and resource 'Shares' are explicit.

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?

It explains that the 'action' parameter selects the endpoint and lists each action with its HTTP method and path. While it doesn't explicitly say when not to use this tool, the context makes it clear that it's for external sharing, and the detailed action list guides usage. No alternative tools are mentioned, but the purpose is distinct.

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