Skip to main content
Glama
nhantruong96

trimble-connect-mcp

by nhantruong96

tc_create_folder_structure

Create a whole folder tree in a Trimble Connect project with a single call, automatically generating intermediate folders and reusing existing paths for safe re-runs.

Instructions

Create a whole folder tree in one call (e.g. an ISO 19650 CDE).

Requires TC_ENABLE_WRITE=1.

Args: project_id: Project ID. paths: Folder paths relative to the start folder, '/' separated, e.g. ["01-WIP/01-ARC", "01-WIP/02-STR", "02-SHARED", "03-PUBLISHED"]. Intermediate levels are created automatically, so listing only the leaves is enough. parent_folder_id: Start folder; omit for the project ROOT. skip_existing: Reuse a folder that already exists instead of failing (default True) — makes the call safe to re-run.

Returns: {"created": [{"path","id"}], "existing": [{"path","id"}], "errors": [{"path","error"}], "root_folder_id": str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYes
project_idYes
skip_existingNo
parent_folder_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses important behaviors beyond the annotations: the TC_ENABLE_WRITE requirement, automatic creation of intermediate levels, the default behavior of skip_existing, and the return structure. It also notes that the call is safe to re-run, providing a nuanced behavioral trait not captured by the idempotentHint=false annotation.

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 well-structured with a clear summary, a requirement note, a detailed Args list with examples, and a return format section. Every sentence adds value, and the layout makes it easy to scan. It is concise for the complexity it covers.

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?

The description is complete for a tool with 4 parameters and a write operation. It covers prerequisites, parameter semantics, default behavior, return values, and a real-world use case. The output schema is described in text, and the annotations are complemented rather than contradicted.

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?

Despite a schema description coverage of 0%, the description explicitly explains every parameter in the Args section, including the format for paths, the meaning of parent_folder_id, and the use of skip_existing. This fully compensates for the lack of schema-level descriptions and adds practical examples.

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's function with a specific verb and resource: 'Create a whole folder tree in one call'. It provides a concrete use case (ISO 19650 CDE) and distinguishes itself from singular folder creation tools like tc_create_folder by emphasizing bulk creation of a hierarchical structure.

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 gives a clear use case and a prerequisite (TC_ENABLE_WRITE=1), but does not explicitly mention alternatives or when not to use it. It implies usage for bulk folder structure creation with the phrase 'in one call', which helps differentiate from sibling tools, but lacks explicit exclusion 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