Paired Plus by Cotlet

Refund sale in Paired Plus

paired_plus_refund_sale

Read-onlyIdempotent

Refund sale 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_refund_sale"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already state readOnlyHint=true and destructiveHint=false; the description adds the important behavioral fact that the tool performs no side effect and must be followed by browser automation, plus the API/onboarding situation that explains why browser steps are needed. No contradiction with annotations, though it does not describe the format or length of the returned instructions.

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 (guidance-only, follow with cotlet_browser_* tools) is front-loaded, but "from ChatGPT, Claude or any AI agent" is filler and the final sentence about the ProSolutions Paired host and missing API key reads as research trivia rather than invocation guidance.

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?

For a zero-parameter, no-output-schema guidance tool with safety annotations already present, the description covers what is returned and how to proceed. It omits edge cases (e.g., sales that are already refunded or user permission requirements), but the essentials for a correct call are there.

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 and full schema coverage, so the baseline is 4. The description adds relevant context about where the work happens (the user's own account, Cloud Browser) rather than leaving the empty-argument call unqualified.

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 names a specific verb and resource ("Refund sale in the user's own Paired Plus account") and, critically, clarifies that the tool returns step-by-step instructions rather than performing the refund ("opens nothing by itself"). The action-sounding name could momentarily mislead, but the second sentence resolves what the tool actually returns.

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 an explicit workflow: call this first to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. There is no explicit "when not to use" or comparison against sibling paired_plus_* tools, but the handoff condition is concrete enough to act on.

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?