Skip to main content
Glama
nhantruong96

trimble-connect-mcp

by nhantruong96

tc_login

Idempotent

Sign in to Trimble Connect via browser OAuth2 to obtain access tokens. Use this before other tools; it returns pending until you complete sign-in.

Instructions

Sign in to Trimble Connect via the browser (OAuth2 + PKCE).

Opens the user's default browser at the Trimble Identity login page and listens on the registered localhost callback (TC_REDIRECT_URI, default http://localhost:8385/callback). Tokens are cached locally and refreshed automatically, so this is only needed the first time or after the session fully expires.

The call does NOT block indefinitely: if the sign-in is not finished within wait_seconds it returns {"pending": true, "auth_url": ...} while the callback listener keeps waiting in the background (up to 10 minutes total). In that case tell the user to finish signing in — opening auth_url manually if no browser appeared — and then call tc_auth_status to confirm. Do NOT immediately call tc_login again; a second call simply waits on the same pending login.

Args: wait_seconds: How long to wait before returning a pending result (default 90). Use a small value to return quickly. open_browser: Set false to only return auth_url without launching a browser (useful when the browser cannot be opened automatically).

Returns: {"logged_in": true, "user": {...}} on success, {"logged_in": false, "pending": true, "auth_url": ...} if the user has not finished yet, or {"error": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
open_browserNo
wait_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description goes far beyond the annotations, detailing the non-blocking behavior, background listener timeout (10 minutes), token caching and auto-refresh, the 'pending' return state, and browser launching behavior. It adds crucial operational context that annotations alone (readOnlyHint, idempotentHint) do not convey, and it is consistent with them.

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

Conciseness5/5

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

The description is structured with clear sections (main explanation, 'Args', 'Returns') and is front-loaded with the core purpose. Despite its length, every sentence serves a functional purpose—explaining behavior, parameters, or user instructions—with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two simple parameters and no output schema shown, the description covers everything: the OAuth flow, callback mechanism, caching, pending behavior, user guidance, parameter semantics, and return contract. It also integrates well with sibling tools (tc_auth_status, tc_login_cancel), making the context complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by explaining both parameters: wait_seconds (default 90, controls how long before returning pending) and open_browser (false returns auth_url without launching). It also documents the return variants, covering what the schema lacks.

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 opens with a clear, specific verb+resource: 'Sign in to Trimble Connect via the browser (OAuth2 + PKCE).' It fully distinguishes the tool from its siblings by framing it as the initial authentication step, explicitly referencing tc_auth_status as the follow-up for pending logins.

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

Usage Guidelines5/5

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

It explicitly states when to use ('only needed the first time or after the session fully expires'), warns against repeated calls ('Do NOT immediately call tc_login again'), and prescribes the correct alternative ('call tc_auth_status to confirm'). This is exemplary usage guidance.

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/nhantruong96/trimble-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server