ChurchSuite Bookings MCP

find_serving_pattern

Retrieve a person's ministry memberships and recurring serving schedule, such as 'fortnightly on Sundays at 09:30', to understand their typical serving pattern.

Instructions

Find which Rotas ministries/teams/roles a person belongs to, and their typical serving pattern.

IMPORTANT: ChurchSuite's API v2 does not expose individual rota slot assignments or dates, only ministry membership and a ministry's recurring schedule definition (days, starts_at/ends_at, rotation_type). This tool cannot tell you the exact next date someone is rostered on; it returns the ministries they serve in plus that ministry's recurrence pattern so you can describe roughly how often/when they serve (e.g. "fortnightly on Sundays at 09:30"). For a confirmed next serving date, the user should check My ChurchSuite directly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "person_id": "<person_id>",
      "person_type": "<person_type>"
    },
    "name": "find_serving_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`person_id`	Yes
`person_type`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

No annotations are provided, so the description fully bears the burden of behavioral disclosure. It transparently explains the API limitation (no individual slot assignments), what data is returned (ministries and recurrence pattern), and what is not (exact dates). This goes well beyond just stating the purpose.

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 well-structured with an important note section. It front-loads the primary purpose. While slightly verbose, every sentence adds value, and the structure aids readability. Could be trimmed slightly without loss.

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?

The tool has an output schema (true) and is moderately complex. The description sufficiently explains what the tool returns (ministries and recurrence pattern) and its limitations. Given the context, it provides complete coverage of what an agent needs to know to use the tool correctly.

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

Parameters2/5

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

Despite having 0% schema description coverage, the description adds no meaning to the two parameters (person_id, person_type). It does not explain the purpose of person_type (enum values) or any relationships. Given low schema coverage, this is a significant gap.

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 clearly states the tool finds which Rotas ministries/teams/roles a person belongs to and their typical serving pattern. It uses specific verbs ('find') and resources ('ministries/teams/roles'), and distinguishes itself by explaining what it cannot do (exact dates), setting it apart from siblings like list_ministry_members.

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?

The description explicitly tells when to use this tool (to get ministry membership and recurrence pattern) and when not (to get exact next serving date). It provides an alternative: 'the user should check My ChurchSuite directly' for confirmed next serving dates. This is excellent guidance.

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

Deploy Server