Skip to main content
Glama
Sign In

Contractor Foreman MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create estimate in Contractor Foreman

contractor_foreman_create_estimate
Read-onlyIdempotent

Create estimate in the user's own Contractor Foreman account from ChatGPT, Claude or any AI agent. Returns how to do it in Contractor Foreman step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Contractor Foreman Cloud Browser. Contractor Foreman's official API: Contractor Foreman has no public API (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": "contractor_foreman_create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself' and only returns instructions. It adds useful context the annotations cannot convey — the return shape (screens, buttons, fields) and the fact that Contractor Foreman has no public API, justifying the browser-based approach. This is a genuine value-add beyond the structured data.

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 prose is somewhat run-on and the trailing 'Contractor Foreman's official API: Contractor Foreman has no public API (checked 11 Oct 2026)' is redundant phrasing with a stale-date detail. It is informative but could be tightened.

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 guidance tool with no output schema, the description covers what it returns, that it performs no action, and how to follow up with browser tools. That is sufficient for an agent to call it correctly; only the relationship to other guide tools is left implicit.

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 the baseline is 4. Nothing in the schema needs explaining, and the description correctly implies no inputs are required to fetch the guidance.

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?

The description states a specific behavior: it returns step-by-step instructions (screens, buttons, fields) for creating an estimate, and explicitly says it 'opens nothing by itself.' It also distinguishes itself from the cotlet_browser_* tools that actually perform the action. The main deduction is that the name/title ('create estimate') suggest a mutation until the description clarifies it is instructional, which slightly taxes the reader.

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 implies the workflow: use this tool to learn the steps, then execute with cotlet_browser_* tools, and notes there is no public API. However, it gives no explicit when-not guidance and does not differentiate from similar guidance tooling such as cotlet_app_guide, leaving the agent to infer the boundary.

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

All Contractor Foreman MCP Server and API by Cotlet toolsInspect
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