Supermove MCP Server and API by Cotlet

Mark job complete in Supermove

supermove_mark_job_complete

Read-onlyIdempotent

Mark job complete in the user's own Supermove account from ChatGPT, Claude or any AI agent. Returns how to do it in Supermove step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Supermove Cloud Browser. Supermove's official API: Supermove has a Developer API, but it brings data in: a New Lead endpoint, a Standard Website endpoint, Add Survey and Update Project, all on a URL unique to your company (checked 28 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": "supermove_mark_job_complete"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the key behavior that this tool 'opens nothing by itself' and returns procedural guidance, which is essential given the mutating-sounding name. The API aside explains why the browser route exists, though it is somewhat tangential.

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 purpose and workflow are front-loaded and useful, but the final sentence about Supermove's Developer API endpoints rambles and only loosely earns its place. Phrasing like 'from ChatGPT, Claude or any AI agent' adds bulk without aiding selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema, read-only guide tool, the description supplies the return format (stepwise screens/buttons/fields) and the follow-up action with browser tools. Nothing an agent needs to call it correctly is missing.

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?

With zero parameters and 100% schema coverage, there is nothing to document; baseline 4 applies. The description correctly implies the tool takes no input and returns instructional text.

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 action and resource and, crucially, clarifies the otherwise misleading name: it returns step-by-step instructions ('screens, buttons, fields') rather than performing the completion. It distinguishes itself from the cotlet_browser_* siblings that actually execute the action.

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 clearly routes the agent: use this tool to get instructions, then carry them out with cotlet_browser_* tools in the Supermove Cloud Browser. There is no explicit exclusion of other Supermove siblings (e.g. supermove_open_project), but the two-step workflow is unambiguous.

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

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