Checkatrade MCP Server and API by Cotlet

Browse Opportunities Board in Checkatrade

checkatrade_browse_opportunities_board

Read-onlyIdempotent

Browse Opportunities Board 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_browse_opportunities_board"
  }
}

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?

Annotations already mark this readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely useful behavior beyond them: the tool performs no navigation and returns procedural guidance. The note about Checkatrade's official API not being available to members adds context on why this manual route exists.

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 message is front-loaded and compact, but the closing API sentence ('checked 31 Oct 2026') is a dangling aside with a confusing date and adds little for an agent choosing a tool. Phrasing like 'Returns how to do it in Checkatrade step by step' is slightly tangled.

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?

With no output schema, the description must explain the return value, and it does: step-by-step screens, buttons and fields. It also covers the follow-up tooling and the constraint that nothing is opened automatically, which is everything an agent needs to invoke and chain this correctly.

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 there is nothing for the description to disambiguate; baseline 4 applies. The empty schema is consistent with a guidance-only tool.

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?

Names a specific resource (Opportunities Board) in the user's own Checkatrade account and states what the tool actually returns: step-by-step guidance (screens, buttons, fields) rather than a live page. The key distinction from the browser siblings is stated ('opens nothing by itself; then do it with the cotlet_browser_* tools'), though the verb 'Browse' in the name slightly misleads about the real output.

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 tells the agent the workflow: call this to get instructions, then perform the actions with cotlet_browser_* in the Checkatrade Cloud Browser. It does not state when NOT to use it (e.g., if the user just wants data instead of a walkthrough), but the sequencing is clear enough to route correctly.

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?