msza.ai — Polish Catholic Sermons ✝

Search public msza.ai sources

search_msza_ai

Read-onlyIdempotent

Search public sermons from the entire msza.ai archive plus sermon studies, Bible passages, prayers, songs, people, and places for focused topic, keyword, or relevance discovery. Use it only when no exact ID or dedicated lookup applies; do not invoke it automatically for every request. Use days_back for rolling periods and date_from/date_to for any absolute historical period. You may call it again with a broader or narrower topic when results are weak. Returns source IDs, stable citation labels, short verbatim excerpts, dates, and links. Priest names are not stored.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of compact source results to return.
`query`	Yes	Focused natural-language search query in Polish or English.
`date_to`	No	Optional last Warsaw calendar day of an absolute archive period, inclusive.
`weekday`	No	Optional Warsaw weekday filter: Sunday=0, Monday=1, ..., Saturday=6.
`camera_id`	No	Optional stable church profile ID. When supplied, only public sermons from that church are searched.
`date_from`	No	Optional first Warsaw calendar day of an absolute archive period, inclusive.
`days_back`	No	Optional rolling calendar-day window ending today, for example 7 or 28. Omit when using date_from or date_to.
`content_types`	No	Optional content categories to search; omitted preserves automatic mixed discovery. Unselected categories are not queried. prayer_book covers prayers, songs and fixed liturgical texts. ai_study results are AI-generated orientation, not evidence. Explicit bible selection enables bounded Scripture search without intent inference. Date/weekday/church filters apply only to sermons; camera_id requires sermon when content_types is supplied. Up to 6 entries; duplicates are removed. Existing source kind labels remain unchanged.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`filters`	Yes
`sources`	Yes
`retrieval`	No
`archiveCapabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

addedInput schema / properties / content_types

Added value: +{
+  "description": "Optional content categories to search; omitted preserves automatic mixed discovery. Unselected categories are not queried. prayer_book covers prayers, songs and fixed liturgical texts. ai_study results are AI-generated orientation, not evidence. Explicit bible selection enables bounded Scripture search without intent inference. Date/weekday/church filters apply only to sermons; camera_id requires sermon when content_types is supplied. Up to 6 entries; duplicates are removed. Existing source kind labels remain unchanged.",
+  "items": {
+    "enum": [
+      "sermon",
+      "ai_study",
+      "prayer_book",
+      "person",
+      "place",
+      "bible"
+    ],
+    "type": "string"
+  },
+  "maxItems": 6,
+  "minItems": 1,
+  "type": "array"
+}

addedOutput schema / properties / filters / properties / content_types

Added value: +{
+  "description": "Normalized requested categories, present only when explicitly supplied.",
+  "items": {
+    "enum": [
+      "sermon",
+      "ai_study",
+      "prayer_book",
+      "person",
+      "place",
+      "bible"
+    ],
+    "type": "string"
+  },
+  "maxItems": 6,
+  "minItems": 1,
+  "type": "array"
+}

Changed6 schema fields changedSep 16, 2026

addedOutput schema / properties / sources / items / properties / content_origin

Added value: +{
+  "enum": [
+    "ai_generated"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / sources / items / properties / prayer_id

Added value: +{
+  "description": "Exact get_prayer argument for a prayer-book search result.",
+  "type": "string"
+}

addedOutput schema / properties / sources / items / properties / recommended_use

Added value: +{
+  "enum": [
+    "topic_orientation_only"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / sources / items / properties / study_id

Added value: +{
+  "description": "Exact get_ai_study argument for an AI-generated study result.",
+  "type": "string"
+}

addedOutput schema / properties / sources / items / properties / usage_guidance
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / sources / items / properties / verification_required
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```

Changed1 schema field changedSep 15, 2026

addedOutput schema / properties / sources / items / properties / licensing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "copyright": {
+      "type": "string"
+    },
+    "license": {
+      "type": "string"
+    },
+    "license_url": {
+      "type": "string"
+    },
+    "source_url": {
+      "type": "string"
+    },
+    "translation": {
+      "type": "string"
+    },
+    "translation_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "translation",
+    "translation_id",
+    "copyright",
+    "license",
+    "license_url",
+    "source_url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of compact source results to return."
```
First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive safety, so the bar is lower. The description adds genuinely useful behavioral context: the search is over the entire archive, results contain stable labels and short excerpts, and priest names are not stored, which prevents futile queries. It does not contradict annotations.

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?

Four sentences with no filler; the first sentence fronts the purpose, the second gives usage boundaries, the third addresses parameter strategy, and the last states outputs and limitations. While dense, every sentence earns its place.

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?

Given the tool's complexity (8 parameters, 6 content types, 13 siblings) and a rich output schema, the description is remarkably complete: it states scope, when-not-to-use, temporal filtering strategy, retry guidance, result contents, and a key data limitation. Nothing critical for correct invocation is missing.

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 meaning beyond the schema by advising when to use days_back vs. date_from/date_to and how to adjust the topic after weak results. It also implicitly warns against searching by priest name, which is a semantic constraint not in the schema.

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 names the specific verb 'Search' and the resource (public msza.ai archive plus sermon studies, Bible passages, prayers, songs, people, and places), which clearly differentiates it from the sibling get_* and list_* tools. The scope is explicit and narrowly tied to the tool's name and title.

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 explicitly states when to use the tool ('only when no exact ID or dedicated lookup applies') and when not to ('do not invoke it automatically for every request'). It also gives concrete parameter-strategy guidance: use days_back for rolling periods and date_from/date_to for absolute historical periods, plus a retry heuristic for weak results.

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

All msza.ai — Polish Catholic Sermons ✝ 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?