Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_todos

Manage Trimble Connect to-dos: list, create, update, delete, and handle attachments and types. Select the action via the "action" parameter.

Instructions

Trimble Connect ToDos: full management incl. details, delete, types, attachments. Select the endpoint with the "action" parameter. Path placeholders {projectId}/{id}/{subId}/{extraId}/{version} are filled from the matching input parameters. Actions:

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

  • get: GET /todos/{id} — id=todoId

  • create: POST /todos — body: {label, projectId, description?, assignees?, dueDate?...}

  • update: PATCH /todos/{id} — id=todoId, body: fields to update

  • delete: DELETE /todos/{id} — id=todoId

  • list_types: GET /todos/types — query: {projectId}

  • list_attachments: GET /todos/{id}/attachments — id=todoId

  • add_attachments: POST /todos/{id}/attachments — id=todoId, body: {attachments:[fileIds]}

  • remove_attachments: DELETE /todos/{id}/attachments — id=todoId, body: {attachments:[fileIds]}

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, so the description bears full responsibility. It discloses all actions, required IDs, and body structures for writes. It does not mention side effects, auth, or errors, but the level of detail (e.g., path placeholder mapping) is commendable.

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 brief intro followed by a bulleted list of actions. It is front-loaded with the general purpose. Though lengthy, every sentence adds value. Minor redundancy (e.g., repeating body structure) could be trimmed.

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 tool's complexity (10 parameters, 9 actions, no output schema), the description covers the action selection, required IDs, and payloads adequately. It lacks output/error details but is fairly complete for agent 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 coverage is 100%, baseline 3. The description adds significant value by explaining the action parameter's role, mapping IDs to path placeholders, and providing example body fields for create/update. This enriches the schema beyond just property 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?

The description clearly states it manages Trimble Connect ToDos with full management incl. details, delete, types, attachments. It lists all 9 actions with HTTP methods and required parameters, distinguishing it from siblings like tc_create_todo or tc_list_todos which are more specialized.

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?

The description explains how to select endpoints via the 'action' parameter and maps each action to HTTP method and path. However, it does not provide guidance on when to use this composite tool versus the more specialized sibling tools (e.g., tc_create_todo, tc_list_todos), leaving the agent without clear usage context.

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