Skip to main content
Glama
Sign In

Contractor+ MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create job in Contractor+

contractor_plus_create_job
Read-onlyIdempotent

Create job in the user's own Contractor+ account from ChatGPT, Claude or any AI agent. Returns how to do it in Contractor+ step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Contractor+ Cloud Browser. Contractor+'s official API: Contractor+ has a public API with an account API key, but it comes with the Pro Team plan, together with Zapier; Freedom and Pro do not include it (checked 8 Nov 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_plus_create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this by stating it 'opens nothing by itself' and only returns guidance — a crucial behavioral disclosure. It also discloses the output nature (screens, buttons, fields) and the plan-gated API constraint. It does not describe exact return structure or any limits, keeping it short of a 5.

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 workflow is front-loaded and useful, but the official-API tangent is wordy and includes an oddly specific 'checked 8 Nov 2026' date that adds little for tool selection. The run-on structure could be tightened into clearer separate statements.

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-param tool with no output schema, the description covers what it does, what it returns, the follow-up action, and why the API route is unavailable. It is nearly complete; only the precise shape of the returned steps 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. The description correctly implies no input is needed and adds no misleading parameter expectations. Nothing further to document.

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 a specific verb+resource ('Create job in the user's own Contractor+ account') and immediately clarifies the real behavior: it returns a step-by-step guide and 'opens nothing by itself.' The name/behavior tension is resolved within the same sentence, and naming cotlet_browser_* tools distinguishes it from siblings. Minor deduction because the opening verb 'Create' slightly oversells what is really a guide-returning tool.

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?

Gives a clear workflow: call this to get steps, then perform them with cotlet_browser_* tools in the Contractor+ Cloud Browser. The API paragraph effectively explains why the direct-API path is not available (plan gating), steering the agent away from a wrong approach. No explicit sibling comparison (e.g., create_estimate) or when-not-to-use-this-tool statement.

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

All Contractor+ 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