Skip to main content
Glama
Sign In
Buildertrend MCP Server

Buildertrend MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

buildertrend_click

Clicks the numbered element you specify on the current Buildertrend page, enabling action on items identified in the last read.

Instructions

Click a numbered element on the current Buildertrend page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "buildertrend_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden and fails to say that a click mutates page state, that it may trigger navigation or form submission, or whether the tool waits for the result. For an interactive browser-automation action with side effects, that is a substantial gap.

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?

One short sentence with no filler, and the action verb and target are front-loaded. Nothing in it could be trimmed without losing content.

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

Completeness2/5

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

For a state-changing interaction tool with no annotations and no output schema, the definition should explain what happens after the click and whether a subsequent read is needed. That information is entirely absent, leaving the agent to guess at the post-click state model.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is fully documented as "Element number from the last read," so the schema does the work. The phrase "numbered element" adds minimal meaning beyond it, warranting the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ("Click") and resource ("a numbered element on the current Buildertrend page") make the action unambiguous and separate it from read/type siblings. It stops short of naming which sibling produces the element numbers (buildertrend_read), so an agent must infer the pairing.

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

Usage Guidelines2/5

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

The description never states when to click versus type or read, nor any precondition such as needing a fresh read first. The only workflow hint ("numbered element") is implicit and the schema carries the actual reference to "the last read."

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools