Skip to main content
Glama
Sign In

Phorest MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Reschedule appointment in Phorest

phorest_reschedule_appointment
Read-onlyIdempotent

Reschedule appointment in the user's own Phorest account from ChatGPT, Claude or any AI agent. Returns how to do it in Phorest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Phorest Cloud Browser. Phorest's official API: Phorest has an API, but credentials come only through Phorest Support with your account number, and Phorest says integration needs your own development team (checked 8 Nov 2026).

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": "phorest_reschedule_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotent, and the description is consistent with them by stating it opens nothing by itself. It adds useful context beyond annotations: the return content shape (screens, buttons, fields) and the reason the official Phorest API isn't used (credentials only via Phorest Support, own dev team required). No rate limits, but none are relevant for a local instruction generator.

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?

Front-loads what the tool does and what it returns, then the follow-up step with browser tools. The closing parenthetical about Phorest's API is longer than necessary but earns partial credit as justification for why this is a guide-only tool.

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 and no output schema, the description carries the burden of describing returns, and it does so (step-by-step screens, buttons, fields). It also explains the required follow-on mechanism. A brief note on failure cases (e.g., appointment not found) is the only missing piece.

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 baseline is 4. The description does not need to explain inputs, and it correctly focuses on output and workflow instead.

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?

Names a specific verb and resource (reschedule appointment) and immediately clarifies this tool only returns step-by-step instructions rather than performing the action. That distinction separates it from the cotlet_browser_* tools, though the 'from ChatGPT, Claude or any AI agent' phrase adds no informational value.

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 states the two-step workflow: call this first to get screens/buttons/fields, then execute with cotlet_browser_* in the Phorest Cloud Browser. It also says the tool opens nothing by itself. It does not explicitly distinguish reschedule from the sibling phorest_book_appointment, but the resource name makes the boundary reasonably clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Phorest MCP Server and API by Cotlet toolsInspect
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