Buildertrend MCP Server and API by Cotlet

Get schedule in Buildertrend

buildertrend_get_schedule

Read-onlyIdempotent

Get schedule in the user's own Buildertrend account from ChatGPT, Claude or any AI agent. Returns how to do it in Buildertrend step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Buildertrend Cloud Browser. Buildertrend's official API: Buildertrend publishes no API docs or self-serve keys for customers; it connects through its Marketplace integrations (checked 11 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buildertrend_get_schedule"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: 'opens nothing by itself' confirms no side effects on the user's account and that output is instructional text with screens/buttons/fields. It also discloses that Buildertrend has no public API or self-serve keys, explaining why a browser-based follow-up is required. Minor gap: no statement about freshness/caching of the instructions.

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

Conciseness3/5

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

The core behavior is front-loaded, but the opening 'from ChatGPT, Claude or any AI agent' is promotional filler, and the trailing note about Buildertrend's API/Marketplace integrations is tangential to invoking this tool. The middle sentence carries nearly all the actionable content.

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?

For a zero-parameter, read-only tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), that nothing is mutated, and what to do next. Only the exact response format and any staleness caveat are left unspecified.

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?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies no arguments are needed by describing the call as a self-contained instruction lookup.

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?

States the resource (Buildertrend schedule) and, importantly, clarifies that the tool returns a step-by-step guide rather than the schedule data itself: 'Returns how to do it in Buildertrend step by step (screens, buttons, fields)'. The name 'get_schedule' slightly oversells retrieval, but the description corrects that immediately and distinguishes the tool from the cotlet_browser_* siblings it hands off to.

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?

Explicitly routes the agent: call this first to obtain instructions, 'then do it with the cotlet_browser_* tools in the user's Buildertrend Cloud Browser'. That is a clear workflow and names the alternative tool family. It stops short of saying when NOT to use it (e.g. if the agent already knows the steps) or what to do on failure.

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

All Buildertrend MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?