Paired Plus by Cotlet

Configure membership rewards in Paired Plus

paired_plus_configure_membership_rewards

Read-onlyIdempotent

Configure membership rewards 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_configure_membership_rewards"
  }
}

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, idempotentHint=true and destructiveHint=false; the description is consistent with these and adds meaningful context by stating it 'opens nothing by itself' and returns screen-by-screen instructions. It also notes the lack of a self-serve API key, which helps the agent understand why browser automation is required. It could say more about the shape/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.

Conciseness4/5

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

The purpose and the crucial non-mutating caveat are front-loaded, followed by the follow-up workflow. The final sentence about the official API is somewhat tangential and awkwardly worded, but it conveys a useful fact that justifies the browser-tool handoff.

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 a read-only annotation profile, the description covers what an agent needs: what it returns, that it mutates nothing, and which tool family to use next. Minor gap is the absence of any detail on format or granularity of the returned steps.

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 beyond what the empty schema already conveys. Baseline 4 applies; no parameter-level gaps exist.

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 (configure membership rewards) and immediately clarifies an important nuance: this tool only returns step-by-step instructions (screens, buttons, fields) and does not itself change anything. That distinguishes it from an executing tool, though it does not explicitly name sibling tools like paired_plus_redeem_rewards, so the agent must infer the boundary.

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?

Clear workflow guidance is given: call this first to obtain the how-to, then carry out the action using the cotlet_browser_* tools in the Paired Plus Cloud Browser. It does not state explicit when-not conditions or name sibling alternatives, but the sequencing instruction is unambiguous.

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?