MszaAI

View saved version →

---
name: explore-homilies
description: Find and compare Catholic homilies (sermons) by topic, Bible passage, date, or parish, with MszaAI source links and explanations in the user's language. Use for requests to find existing homilies, compare sermon interpretations, or prepare Bible-study and small-group discussion questions grounded in retrieved homilies; also for explicit requests for MszaAI daily readings, prayers, or public parish material. When asked to record, modify, or publish through MszaAI, explain its read-only limits. Do not activate for general theology, writing a sermon without requested sources, or standalone translation of supplied text.
---

# Explore Catholic homilies

Use the connected MszaAI MCP tools to answer the requested question from public sources. Respect the user's chosen language, scope, and format. The archive is mainly Polish and covers participating churches; it is not a worldwide parish directory or a representative account of Catholic teaching.

## Retrieval budget and stopping conditions

For topic discovery, call `search_msza_ai` with `limit: 5`; this tool accepts only integers from 1 through 8. For one user request, make at most two topic-search calls in total: the initial focused query and, only if needed, one constrained Polish rephrase. Call `get_sermon` at most five times. Count repeated and failed calls toward these limits; reuse successful results instead of repeating an identical query. Stop at these limits even when fewer sources than requested are confirmed; explain the shortfall using the evidence already retrieved. Do not restart this budget through another topic, language, tool, browser, or parallel branch.

On HTTP 429 or another rate-limit response, stop all MszaAI retrieval for this request immediately. Do not retry the failed call, queue another source, or switch tools or browsers. Report the available retry guidance, or say that no retry time was supplied. Use only already verified material; when none is available, explain the limitation without substituting general Scripture or theology commentary for the requested homilies.

For a Bible-passage request, use the saved-annotation lookup. If it returns no matches and no continuation cursor, stop and report the index status. Do not switch to keyword searches or inferred themes to manufacture passage-linked results. A broader thematic search is a separate option the user can request.

If the user explicitly asks MszaAI to record, modify, or publish content, explain that this plugin only reads public material. Do not launch a browser or another service to perform the unsupported MszaAI action.

## Retrieve in the source language, answer in the user's language

- Interpret the user's request in any language. For topic retrieval, translate the concept into a short Polish query before `search_msza_ai`; keep public proper names, exact IDs, and Bible references intact. For example, an English request about forgiveness can use `query: "przebaczenie"`. Avoid long translated sentences or lists of synonyms that narrow the text search unnecessarily.
- Send only the topic and necessary public filters, not the conversation, personal circumstances, private names, confessions, or sensitive details. Do not ask for credentials or a MszaAI account: this connection reads public content.
- Keep date, church, passage, and content-type constraints unchanged when translating. Use `content_types: ["sermon"]` for homilies. Other categories are `ai_study`, `prayer_book`, `person`, `place`, and `bible`; search only the requested categories.
- Return the explanation in the user's language unless they request another. Tools return saved source text; translation and synthesis happen in the conversation. Identify translated excerpts as translations and distinguish them from your explanation. Do not promise a published translation in the archive.

## Choose the direct route

| User's intent | Tool and handling |
| --- | --- |

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.