ServiceTrade MCP Server and API by Cotlet

Add comment to job in ServiceTrade

servicetrade_add_comment_to_job

Read-onlyIdempotent

Add comment to job 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_add_comment_to_job"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the annotations by stating that the tool opens nothing by itself and returns screens, buttons, and fields. This aligns with readOnlyHint=true and makes clear the mutation is performed later through browser tools.

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 critical operational detail is present but buried after marketing-style phrasing about ChatGPT, Claude, or any AI agent. The final sentence about ServiceTrade's official API is background information that does not help an agent invoke this tool.

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 guidance tool with no output schema, the description sufficiently explains what it returns and how the subsequent browser-based flow works. Minor API background is unnecessary but not harmful.

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?

There are zero input parameters, so the baseline is 4. The description correctly does not imply any required inputs and directs the agent toward the browser tools for execution.

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 clearly states the resource and action: adding a comment to a job in the user's own ServiceTrade account. It also clarifies the tool returns step-by-step guidance rather than performing the change itself, which is important for interpreting the name correctly.

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?

It explains the intended workflow: get instructions here, then execute with cotlet_browser_* tools. However, it does not explicitly compare this with other ServiceTrade sibling tools or state when not to use this guidance flow.

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?