Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_companies

Manage Trimble Connect companies and their members. List, get, update companies, add or remove users and email domains.

Instructions

Trimble Connect Companies and company members. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • list: GET /companies

  • get: GET /companies/{id} — id=companyId

  • update: PATCH /companies/{id} — id=companyId, body: fields to update

  • list_users: GET /companies/{id}/users — id=companyId

  • add_users: POST /companies/{id}/users — id=companyId, body: users to add

  • update_user: PATCH /companies/{id}/users/{subId} — id=companyId, subId=userId, body: role...

  • remove_user: DELETE /companies/{id}/users/{subId} — id=companyId, subId=userId

  • remove_users: DELETE /companies/{id}/users — id=companyId, body: users to remove

  • add_domains: PATCH /companies/{id}/domains — id=companyId, body: email domains to add

  • remove_domains: DELETE /companies/{id}/domains — id=companyId, body: email domains to remove

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 provided. Description compensates by detailing HTTP methods (GET, PATCH, POST, DELETE) for each action, implying read/write/destructive nature. Explains path placeholders and parameter mapping, but could be more explicit about side effects or prerequisites.

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?

Description is front-loaded with purpose and structured as a clear list of actions. Slightly lengthy but each sentence adds unique information. No redundant statements.

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 complexity (10 actions, 10 parameters, no output schema), description covers all actions with parameter mapping. Lacks return value descriptions, but actions are standard REST and implied by HTTP method. Adequate for selection and invocation.

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 has 100% coverage. Description adds value by explaining how parameters like id, subId, extraId fill path placeholders, and that body is used for POST/PUT/PATCH/DELETE. Goes beyond simple schema descriptions.

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?

Description clearly states it handles Trimble Connect Companies and company members, enumerates 10 distinct actions (list, get, update, list_users, etc.), and distinguishes from sibling tools which cover other resources (projects, files, BCF topics).

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?

Actions are listed with HTTP methods and paths, but no explicit guidance on when to use this tool vs alternatives among the many tc_* siblings. Usage is implied by resource focus, but lacks 'when-not' or comparison.

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