Skip to main content
Glama
SimonTrim

Trimble Connect MCP Server

by SimonTrim

tc_views2d

Manage 2D views in Trimble Connect projects. List, get, create, update, or delete views with specified region and project ID.

Instructions

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

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

  • get: GET /views2d/{id} — id=viewId

  • create: POST /views2d — body: Create2DViewRequest

  • update: PATCH /views2d/{id} — id=viewId, body: fields to update

  • delete: DELETE /views2d/{id} — id=viewId

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 must disclose behavioral traits. It fails to mention destructive consequences (e.g., delete action permanently removes data), authorization requirements, rate limits, or idempotency of updates. For a tool with delete and update actions, this is a significant gap.

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 relatively concise, with three sentences and a bullet list. It front-loads the purpose and action list. However, the bullet list could be more readable (e.g., separating each action into a line). Overall, minimal waste.

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

Completeness3/5

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

Given 10 parameters and no output schema, the description does a good job explaining how parameters relate to actions. However, it does not describe return values or error handling, which would help agents understand tool output. With no output schema, this is a moderate gap.

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?

The description adds substantial value beyond the input schema by explaining which parameters are required for each action and how path placeholders are filled. The schema alone does not provide this action-parameter mapping, yet coverage is 100%.

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 Trimble Connect 2D Views and lists the five CRUD actions (list, get, create, update, delete) with HTTP methods and paths. This distinguishes it from sibling tools like tc_views (for views, not 2D views) and tc_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 Guidelines4/5

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

The description explains how to choose an action using the 'action' parameter and how path placeholders map to input parameters. It provides explicit mapping for each action, but does not state when not to use this tool or mention alternatives like tc_api_call for custom endpoints.

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