Skip to main content
Glama
chrischall

simplepractice-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

simplepractice_list_billing_items

Read-only

Retrieve invoices, statements, superbills, receipts, or account history from the SimplePractice Client Portal. Paginate with a cursor to view more items.

Instructions

Invoices, statements, superbills, receipts, or account history from the Client Portal. An empty list is a real answer — many practices bill entirely outside the portal. Pages by cursor: pass the returned nextCursor as "before".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoinvoice
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.
beforeNoCursor for the next page — the nextCursor from a previous call.
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. Changed1 schema field changedv0.4.1
    • 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

A4.1/5.0
Behavior4/5

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

Annotations already mark the call read-only; the description adds behavioral facts that annotations cannot, including that an empty list is a legitimate answer and that pagination uses a cursor that must be fed back as before. It does not mention rate limits or output format, but the main call semantics are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences front-load the resource scope, then add the empty-list caveat and pagination rule. No content is repeated from the schema or annotations.

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 an optional-parameter read-only list tool, it covers the unusual behaviors that would otherwise trip up an agent: empty list semantics and cursor pagination. It does not describe the actual shape of returned records, but since there is no output schema and the view parameter describes shapes, a fuller description would add bulk without much call-time value.

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 prose maps the kind enum values and explains the before cursor beyond the schema's bare 'Cursor for the next page'. It leaves pageSize to schema defaults and view to the schema's long description, which is reasonable given their self-describing names.

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 enumerates the exact resource types returned (invoices, statements, superbills, receipts, account history) and scopes them to the Client Portal, clearly distinguishing them from sibling list tools. It lacks an explicit verb, but 'list' in the tool name plus the object list make the operation obvious.

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 provides clear context: this is the tool for Client Portal billing documents, and an empty result is meaningful rather than an error, which is important for deciding whether a practice uses the portal. It does not name alternatives such as get_billing_overview or list_payment_methods, so it stops short of explicit exclusionary guidance.

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