StudioVector: Chat with your Mindbody

Clients who may not renew

clients_at_risk

Read-onlyIdempotent

Lists clients at one site who may not renew, with the reasons, contact details and consent flags. Reasons: a membership ending within withinDays with no active autopay to renew it; a Mindbody status of Declined, Suspended or Terminated while still holding a membership or pack; a class pack running low (pack_running_low), or expiring with sessions still left (pack_expiring), with nothing to replace it; and, for a sample of paying clients, no visits in inactiveDays or visits down by half against the 90 days before. Clients whose dates come first are listed first, and "coverage" says what was read and what was left out. Mindbody calls: 1 per 200 client profiles (up to 20), 1 per 200 clients for memberships (up to 20), 1 per 200 clients without a membership for packs (up to 20), 1 per membership whose autopay is checked (maxRenewalChecks, default 10) and 1 per client whose visits are checked (maxVisitChecks, default 10) (at most 110). Check SendPromotionalEmails/Texts before sending marketing. Use client_overview for one client's details.

Input Schema

Name	Required	Description
`limit`	No	Clients to return, 1-50 (default 25). atRisk and byReason count every client flagged.
`siteId`	No	Site to call (SiteId header). Default -99.
`signals`	No	Which reasons to look for (default all): renewals = memberships ending and Mindbody statuses; packs = class packs running low or expiring (1 call per 200 clients without a membership); visits = no or fewer recent visits for a sample of paying clients. signals ["renewals"] with maxRenewalChecks 0 is the cheapest call: statuses only.
`withinDays`	No	Days ahead in which a membership ending or a pack expiring counts, 7-90 (default 30).
`lowSessions`	No	A pack with this many sessions left or fewer is running low, 0-5 (default 1). A pack with more left that expires within withinDays is expiring.
`inactiveDays`	No	The recent window for visits, ending yesterday, 14-90 (default 30). Visits are compared with the 90 days before it.
`maxVisitChecks`	No	Paying clients whose visit history is read, 0-25 (default 10; 1 Mindbody call each), least recently updated profile first.
`maxRenewalChecks`	No	Memberships ending soonest whose contracts are read to see if autopay renews them, 0-25 (default 10; 1 Mindbody call each). Others ending in the window are counted in coverage, not listed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description goes further by quantifying Mindbody call costs per 200 profiles and the 110-call ceiling, plus noting that sampling and truncation happen. It also discloses a return-side behavior: a 'coverage' field saying what was read and omitted, and clients sorted by earliest date.

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?

Sentences are front-loaded and dense with useful detail, but the long run-on enumeration of reasons and the nested call-cost listing make it hard to scan, and there is a duplicated word typo ('within withinDays').

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

Completeness5/5

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

For an 8-parameter, no-output-schema tool, the description covers sorting, truncation, the coverage/summary fields, and cost ceilings — everything an agent needs before spending up to 110 Mindbody calls.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains how withinDays, lowSessions and inactiveDays interact (packs with more sessions left but expiring within the window) and frames maxRenewalChecks/maxVisitChecks as per-call cost drivers with least-recently-updated sampling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Lists clients at one site who may not renew') and enumerates the exact risk reasons (autopay expiry, Mindbody statuses, low/expiring packs, visit decline). This clearly distinguishes it from the single-client sibling, which is named explicitly.

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

Usage Guidelines5/5

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

It names the alternative ('Use client_overview for one client's details') and gives a concrete cost-based configuration ('signals ["renewals"] with maxRenewalChecks 0 is the cheapest call: statuses only'). It also states a precondition for downstream marketing actions (check SendPromotionalEmails/Texts).

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

All StudioVector: Chat with your Mindbody 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?