Paired Plus by Cotlet

Reconcile pms night audit in Paired Plus

paired_plus_reconcile_pms_night_audit

Read-onlyIdempotent

Reconcile pms night audit 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_reconcile_pms_night_audit"
  }
}

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 idempotentHint=true, and the description reinforces this with "opens nothing by itself," which is exactly the kind of clarification an agent needs so it does not assume the reconciliation was executed. It does not describe the shape of the returned instructions (length, format, whether it varies by account configuration).

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 core is two tight sentences that front-load the action and immediately bound it. The trailing note about the ProSolutions Paired API host and the absence of a self-serve API key is tangential to invoking this tool and reads as unstructured background rather than actionable 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, read-only guidance tool with no output schema, the definition covers what it returns (step-by-step screens, buttons, fields), what it does not do, and the follow-up toolset to use. Missing only detail on instruction format or any dependency on the user's account state.

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 the schema carries no semantic burden and the description has nothing to compensate for. Baseline 4 applies.

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 states a concrete verb and resource ("Reconcile pms night audit in the user's own Paired Plus account") and then clarifies that the tool actually returns step-by-step instructions rather than performing the action. That clarification is valuable because it corrects an otherwise misleading name, though it is buried in the second clause rather than front-loaded.

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: call this to get 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 a sibling alternative, which keeps it below a 5.

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?