Skip to main content
Glama
chrischall

simplepractice-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

simplepractice_list_appointments

Read-only

List appointments from the SimplePractice client portal by status: scheduled for confirmed/upcoming visits, requested for those awaiting confirmation, with page-based pagination.

Instructions

Appointments from the Client Portal. status "scheduled" returns confirmed/upcoming ones; "requested" returns those still awaiting the practice's confirmation. Pages by number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; "full" returns SimplePractice's whole records.
statusNoWhich side of the pending-confirmation filter to read.scheduled
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.4.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "default": true,
-  "description": "Return a slim projection. Set false for the full records.",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns SimplePractice's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations include readOnlyHint=true, and the description aligns with this by describing a read-only operation. The description adds value beyond annotations by explaining status semantics and pagination behavior. It does not disclose any side effects, which is appropriate given the readOnly hint, but it could have mentioned response shape or pagination details more thoroughly.

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 description is concise, two sentences, and directly states the core function and key filtering. It front-loads the main purpose and then explains status values. There is no fluff, and it is easy to scan. It could be slightly more explicit about listing, but overall it is well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with a readOnly annotation, the description covers status and pagination. It does not describe the output structure, but there is no output schema to rely on. It also does not mention default behavior for pageSize, but that is in the schema. The description is adequate but not exhaustive; an agent might need to infer some details about the response format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has descriptions for 'view' and 'status', covering 50% of parameters. The description adds meaning for 'status' by explaining the two values, and for 'page' via 'Pages by number'. However, it does not address 'pageSize', and the coverage is only partial. The description partially compensates for the schema gaps but not fully.

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 clearly indicates the tool returns appointments from the Client Portal and clarifies the meaning of the status filter. However, it lacks an explicit verb like 'list' or 'retrieve', relying on the tool name for that. It is distinct from siblings as no other tool lists appointments, so it is adequately differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two status values and pagination, which informs usage. However, it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions. Since no sibling provides the same functionality, the lack of explicit guidance is not critical but still a gap.

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

Deploy Server

Other Tools