Paired Plus by Cotlet

Close register in Paired Plus

paired_plus_close_register

Read-onlyIdempotent

Close register in the user's own Paired Plus account from ChatGPT, Claude or any AI agent. Returns how to do it in Paired Plus step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser. Paired Plus's official API: The ProSolutions Paired host publishes API help, but no self-serve API key or onboarding guide was found.

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": "paired_plus_close_register"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the tool returns screens/buttons/fields as a procedure and performs no action itself, and it notes that no self-serve API key exists, explaining why browser automation is the route. It does not describe the shape or length of the returned guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key fact — that this returns a procedure and does nothing itself — is front-loaded in the first two sentences. The trailing sentence about the ProSolutions Paired host and missing API key is somewhat tangential and awkwardly worded, but it does justify the browser-tool handoff rather than being pure filler.

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 zero parameters, no output schema and rich annotations, the description carries what an agent needs: what is returned (a step-by-step procedure), that nothing is executed, and what to do next. The only gap is the absence of detail on how the returned instructions are structured or how to pass them to the browser tools.

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 and no parameter explanation is required. The description correctly implies no inputs are needed to retrieve the procedure, adding nothing misleading about arguments.

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 verb and resource ('Close register in the user's own Paired Plus account') and immediately clarifies the actual deliverable: step-by-step instructions rather than a performed action. That distinction from a browser-executing sibling is stated, though the phrasing is slightly indirect ('Returns how to do it in Paired Plus step by step').

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 clear operating context ('from ChatGPT, Claude or any AI agent'), an explicit non-behavior ('opens nothing by itself'), and a concrete follow-up path ('then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser'). It stops short of naming which specific browser tool to pair with or stating exclusions, so it is strong but not complete.

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

All Paired Plus 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?