Paired Plus by Cotlet

Reschedule appointment in Paired Plus

paired_plus_reschedule_appointment

Read-onlyIdempotent

Reschedule appointment 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_reschedule_appointment"
  }
}

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?

The description is consistent with the annotations: readOnlyHint=true and destructiveHint=false match 'opens nothing by itself'. It adds value beyond the annotations by disclosing what is actually returned (screens, buttons, fields) and that the real action must be performed with the browser tools. A 5 would require details such as whether the guide reflects the user's specific appointment or a generic flow.

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 (returns steps, performs nothing, act with browser tools) is front-loaded and useful, but the trailing sentence about ProSolutions Paired API help and the absence of a self-serve API key is tangential and blurs the tool's purpose. The first sentence also runs long and mixes audience description with behavior.

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 tool, the description covers the essentials: what is returned, that nothing is executed, and what the agent should do next. The unresolved gap is whether the returned steps are tailored to the user's account or generic, which matters for a rescheduling workflow.

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 and the baseline of 4 applies. The description does not suggest any hidden inputs, which is consistent with the empty schema.

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 gives a specific verb and resource (reschedule an appointment in Paired Plus) and then corrects a likely misreading by stating it 'returns how to do it... step by step' and 'opens nothing by itself'. That makes clear it is a guidance tool rather than an executing one. It does not differentiate itself from the many sibling appointment tools (cancel, create, book), so it stops short of a 5.

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 states the context of use (from ChatGPT, Claude or any AI agent) and explicitly names the follow-up path: act via the cotlet_browser_* tools in the Paired Plus Cloud Browser. What is missing is a 'do not use when' clause or a pointer to a sibling for related tasks such as canceling or creating an appointment.

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?