Paired Plus by Cotlet

Sell membership in Paired Plus

paired_plus_sell_membership

Read-onlyIdempotent

Sell membership 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_sell_membership"
  }
}

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=true and destructiveHint=false, and the description is consistent with that ("opens nothing by itself"). Beyond the annotations it discloses genuinely useful behavior: the tool returns a step-by-step procedure of screens/buttons/fields and requires a separate browser tool to actually act, which an agent must know to chain calls correctly. The trailing note about no self-serve API key adds limited behavioral value.

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 purpose and the "returns steps, does nothing itself" caveat are front-loaded and each sentence carries a distinct point. The final sentence about the ProSolutions Paired host API is somewhat tangential for a zero-parameter tool and slightly dilutes an otherwise tight definition.

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 and no output schema, the description correctly explains what comes back (a step-by-step procedure) and what must happen next (execution via cotlet_browser_* tools). That covers what an agent needs to call and chain it correctly; only the exact shape of the returned steps is left unspecified.

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 parameters, so the baseline is 4 and the description has nothing to compensate for. It correctly implies the account context comes from the authenticated session rather than an argument.

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?

"Sell membership in the user's own Paired Plus account" gives a specific verb and resource that is distinguishable from siblings such as sell_gift_card or sell_service_series, and it adds the key nuance that the tool returns instructions rather than performing the sale. It stops short of explicitly naming which sibling to pick instead, so it is clear but not optimally differentiated.

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?

The description states the operating context (invoked by an AI agent from ChatGPT/Claude) and the follow-up path: the tool returns steps and then the agent should execute them with cotlet_browser_* tools in the user's Cloud Browser. It does not state exclusions or contrast with the many other sell_* siblings, so it is clear guidance without alternatives.

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?