Skip to main content
Glama

simplepractice_list_appointments

Read-only

List SimplePractice Client Portal appointments by status—scheduled for confirmed/upcoming or requested for pending 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.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
viewNocompact returns the slim projection where one exists and strips image URLs elsewhere; "full" returns SimplePractice's whole records. "brief" answers one text line per item — title — <ISO date or "no date"> — <status> — for a host that only needs to say what is there, with "-- " note lines for an empty or full page.
statusNoWhich side of the pending-confirmation filter to read.scheduled
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / view / description
      Previous value: -"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."New value: +"compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns SimplePractice's whole records. \"brief\" answers one text line per item — title — <ISO date or \"no date\"> — <status> — for a host that only needs to say what is there, with \"-- \" note lines for an empty or full page."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full"
      -]New value: +[
      +  "brief",
      +  "compact",
      +  "full"
      +]
  2. 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"
  3. 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"
      +}
  4. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail about the status filter semantics and that results are paginated by number, but says nothing about the 50-item page cap, ordering, or how an empty/full page is signaled beyond the schema's own view description.

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?

Three short sentences, front-loaded with the resource and then the parameter semantics; nothing is redundant. The terse fragment style ("Pages by number.") is efficient but slightly telegraphic rather than fully explanatory.

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?

With four optional parameters, no output schema, and only half the params documented in schema, the description covers status and pagination conceptually but omits the view projection behavior and the page-size ceiling. It is adequate to call the tool correctly if the agent also reads the schema, but not self-sufficient.

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?

Schema coverage is 50%, with view and status carrying heavy inline descriptions, so the schema does most of the work. The description adds meaning only for status (mapping values to confirmed/upcoming vs pending), while page and pageSize get no explanation beyond "pages by number" and the pageSize maximum of 50 is never mentioned.

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?

"Appointments from the Client Portal" names the resource and its source scope, and the status sentence clarifies which slice of appointments is returned. It is clear what the tool does, though it never uses an explicit verb like "list" and does not distinguish itself from the nearby session_status sibling.

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 how to choose between the two status values (confirmed/upcoming vs awaiting practice confirmation), which is genuine when-to-use guidance. It gives no guidance on when to use this tool rather than session_status or other list tools, so usage is only implied at the tool-selection level.

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