Checkatrade MCP Server and API by Cotlet

Request a review in Checkatrade

checkatrade_request_a_review

Read-onlyIdempotent

Request a review in the user's own Checkatrade account from ChatGPT, Claude or any AI agent. Returns how to do it in Checkatrade step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Checkatrade Cloud Browser. Checkatrade's official API: Checkatrade has an official API, but not for members (checked 31 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": "checkatrade_request_a_review"
  }
}

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 readOnly, idempotent and non-destructive; the description adds the crucial behavioral fact that it 'opens nothing by itself' and returns screens/buttons/fields instead of acting. It also notes that no member-facing official API exists, explaining why browser automation is required.

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 instruction is front-loaded and useful, but the single run-on sentence mixes purpose, return format, follow-up tooling and an API aside with a stray future date ('checked 31 Oct 2026'). The 'from ChatGPT, Claude or any AI agent' phrasing is filler that does not help an agent invoke the 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?

With no parameters, no output schema and full annotation coverage, the description supplies what it must: what the call returns (step-by-step screens/buttons/fields) and what to do next. It could add a precondition (user logged into Checkatrade in the Cloud Browser) but the essentials are present.

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 inputs are needed and focuses on what the call yields.

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 and resource ('Request a review in the user's own Checkatrade account') and clarifies that the tool returns instructions rather than performing the action. The distinction from siblings is only indirect, via the pointer to cotlet_browser_* tools, but the purpose is unmistakable.

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?

Explicitly routes the agent: call this first to get the step-by-step guide, then carry it out with the cotlet_browser_* tools in the Checkatrade Cloud Browser. No explicit when-not-to-use or alternative for other review-related flows, but the two-step workflow is clear.

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

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