Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_users

Manage Trimble Connect user profiles, update account settings, and retrieve licenses, timezones, and language preferences. Supports actions: get, update, licenses, timezones, languages.

Instructions

Trimble Connect Users: profiles, update, licenses, timezones, languages. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

  • get: GET /users/{id} — id=userId (or 'me')

  • update: PATCH /users/{id} — id=userId, body: fields to update

  • licenses: GET /users/licenses — current user's licenses

  • timezones: GET /users/timezones

  • languages: GET /users/languages

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 carries the full burden. It discloses HTTP methods and basic behavior (e.g., 'update' uses PATCH), but does not mention side effects, authentication needs, rate limits, or idempotency. For a mutation tool, this is insufficient.

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 well-structured with a bulleted list of actions. Each sentence provides useful information, though it could be more concise. It is appropriately front-loaded with the general purpose.

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 complexity of a multi-endpoint tool with 10 parameters and no output schema, the description covers action selection, parameter mapping, and path placeholders. It lacks response details but is otherwise complete for its purpose.

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% coverage with descriptions, but the description adds value by explaining how path placeholders map to parameters (e.g., 'id=userId (or me)' for get action). This enhances understanding beyond 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 it covers Trimble Connect Users actions: profiles, update, licenses, timezones, languages. It lists specific actions with HTTP methods and paths, distinguishing it from sibling tools like tc_get_current_user or tc_list_project_users.

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?

The description explains to select the endpoint via the 'action' parameter and lists each action with its path and required parameters. It provides clear context for when to use each action, though it does not explicitly exclude alternatives or mention when not to use this tool.

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