Paired Plus by Cotlet

Issue room credit in Paired Plus

paired_plus_issue_room_credit

Read-onlyIdempotent

Issue room credit 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_issue_room_credit"
  }
}

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?

It usefully confirms the read-only nature the annotations declare, stating explicitly that it "opens nothing by itself" and returns step-by-step screens/buttons/fields. It also discloses that no self-serve API key exists for Paired Plus, which explains why browser automation is required.

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 workflow is front-loaded and clear, but the phrase "from ChatGPT, Claude or any AI agent" is promotional padding, and the trailing note about the ProSolutions Paired host and missing API key does not help an agent decide or invoke.

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 input parameters and no output schema, the description covers what the agent gets back (step-by-step guidance) and the exact follow-up tool family to use. It leaves open whether the returned steps are tailored to a specific room or amount, which is a minor gap for a parameterless guide tool.

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 no schema semantics to supplement; the baseline for a parameterless tool applies. The description correctly implies the call is self-contained and returns guidance rather than requiring inputs.

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 ("Issue room credit") and scopes it to the user's own Paired Plus account. It does not, however, distinguish this from the closely named sibling paired_plus_post_room_charge, so an agent must infer which credit-style operation applies.

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 operational context: the tool returns instructions and "opens nothing by itself," then the actual work is done via cotlet_browser_* tools in the user's Cloud Browser. It lacks explicit when-not guidance and any comparison against sibling Paired Plus credit/charge tools.

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?