ServiceTrade MCP Server and API by Cotlet

Create quote in ServiceTrade

servicetrade_create_quote

Read-onlyIdempotent

Create quote in the user's own ServiceTrade account from ChatGPT, Claude or any AI agent. Returns how to do it in ServiceTrade step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ServiceTrade Cloud Browser. ServiceTrade's official API: ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 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": "servicetrade_create_quote"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them by stating the tool 'opens nothing by itself'. It adds genuinely useful behavior beyond the annotations: the return value is a step-by-step UI walkthrough, and the actual mutation happens through cotlet_browser_* tools. The aside about ServiceTrade's REST API and lack of an official MCP server is informational rather than behavioral.

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 first two sentences are front-loaded and do real work: purpose, return shape, and the handoff to browser tools. The final sentence about ServiceTrade's public REST API, OAuth2 and the absence of an official MCP server does not help an agent select or invoke this tool and reads as vendor positioning.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does: step-by-step screens, buttons and fields. It also tells the agent what to do next. Only the relationship to adjacent ServiceTrade quote 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 and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing because none exist.

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 resource (a ServiceTrade quote) and clarifies the tool's real output: step-by-step screens, buttons and fields rather than an executed creation. That resolves the misleading name 'create_quote' and separates it from actual write tools. It stops short of naming a sibling like servicetrade_submit_quote as the alternative for a real submission, so it is clear but not fully differentiated.

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?

It gives a concrete two-step workflow: call this to get instructions, then act with the cotlet_browser_* tools in the ServiceTrade Cloud Browser. That is usable context for an agent deciding how to proceed. It does not state when to prefer this over servicetrade_submit_quote or when this guide is unnecessary.

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

All ServiceTrade 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?