Paired Plus by Cotlet

List waitlist in Paired Plus

paired_plus_list_waitlist

Read-onlyIdempotent

List waitlist 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_list_waitlist"
  }
}

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 cover readOnly, idempotent, non-destructive, non-open-world. The description adds real behavioral context beyond them: no side effects ('opens nothing by itself'), the return shape (screens, buttons, fields), and an operational caveat that no self-serve API key exists, which explains why the browser tools are required. It does not mention pagination or result-size behavior, but for a zero-parameter instruction-generating tool that is minor.

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 two sentences are front-loaded and efficient, but the trailing API note ('The ProSolutions Paired host publishes API help, but no self-serve API key or onboarding guide was found') is awkwardly phrased and reads as research provenance rather than actionable guidance. It earns only partial keep as justification for 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 output schema, the description correctly compensates by describing what comes back ('how to do it step by step (screens, buttons, fields)'). Combined with the follow-up-tool routing and the no-API caveat, an agent has enough to call and act on it. Only minor gaps (no mention of failure modes or account-selection assumptions) remain.

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. Baseline for a parameterless tool applies, and the description correctly makes no parameter claims.

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?

States a specific verb and resource: 'List waitlist in the user's own Paired Plus account.' The resource (waitlist) is distinct from the many sibling list tools (clients, sales, appointments), so an agent can tell them apart on resource alone. It stops short of naming a contrasting sibling or clarifying scope boundaries with the other list_* tools.

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?

Explicitly sets the workflow: this tool returns step-by-step instructions and 'opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser.' That routes the agent to a follow-up tool. It gives no exclusions or conditions distinguishing this from the other paired_plus_list_* 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?