msza.ai — Polish Catholic Sermons ✝

Get a public sermon transcript

get_sermon

Read-onlyIdempotent

Returns public sermon text for an exact session ID in its stored language. text_type identifies an AI-edited transcript section, fallback summary, or fallback short thought; these forms are not guaranteed verbatim speech. truncated and total_chars describe text completeness. references contains at most 50 saved annotations; selected_section concerns the displayed section and session can concern other liturgy. Saved annotations can be machine-generated and incomplete.

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Exact public sermon session ID returned by search_msza_ai or a sermon-listing tool.

Output Schema

Name	Required	Description
`url`	Yes
`title`	Yes
`church`	Yes
`source`	Yes
`text_type`	Yes	Origin of the selected text, not a guarantee of verbatim speech.
`truncated`	Yes	Whether the selected text exceeded the 6000-character response limit.
`references`	Yes	Saved, potentially machine-generated annotations, not verified facts. selected_section covers the selected section before text truncation; session may refer to any part of the liturgy. Not all mentions are necessarily annotated. Use person/place IDs with their get tools. Pass prayer_id to get_prayer for any prayer-book entry including songs and liturgical texts. For Bible passages search by title to resolve passage coordinates.
`session_id`	Yes
`started_at`	Yes
`transcript`	Yes
`total_chars`	Yes	UTF-16 code units in the selected text after whitespace normalization, before response truncation; excludes the added ellipsis.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 16, 2026

changedOutput schema / properties / references / description

Previous value: -"Saved, potentially machine-generated annotations, not verified facts. selected_section covers the selected section before text truncation; session may refer to any part of the liturgy. Not all mentions are necessarily annotated. Use person/place/prayer IDs with the matching get tool. For songs and liturgical texts use the URL or search_msza_ai; for Bible passages search by title to resolve passage coordinates."New value: +"Saved, potentially machine-generated annotations, not verified facts. selected_section covers the selected section before text truncation; session may refer to any part of the liturgy. Not all mentions are necessarily annotated. Use person/place IDs with their get tools. Pass prayer_id to get_prayer for any prayer-book entry including songs and liturgical texts. For Bible passages search by title to resolve passage coordinates."

addedOutput schema / properties / references / properties / items / items / properties / prayer_id
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```

addedOutput schema / properties / source / properties / content_origin

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

addedOutput schema / properties / source / properties / prayer_id

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

addedOutput schema / properties / source / properties / recommended_use

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

addedOutput schema / properties / source / properties / study_id

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

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

Changed6 schema fields changedSep 15, 2026

addedOutput schema / properties / references

Added value: +{
+  "additionalProperties": false,
+  "description": "Saved, potentially machine-generated annotations, not verified facts. selected_section covers the selected section before text truncation; session may refer to any part of the liturgy. Not all mentions are necessarily annotated. Use person/place/prayer IDs with the matching get tool. For songs and liturgical texts use the URL or search_msza_ai; for Bible passages search by title to resolve passage coordinates.",
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "maxLength": 160,
+            "minLength": 1,
+            "type": "string"
+          },
+          "kind": {
+            "enum": [
+              "person",
+              "place",
+              "bible",
+              "song",
+              "prayer",
+              "liturgical"
+            ],
+            "type": "string"
+          },
+          "scope": {
+            "enum": [
+              "selected_section",
+              "session"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "maxLength": 300,
+            "type": "string"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "kind",
+          "id",
+          "title",
+          "url",
+          "scope"
+        ],
+        "type": "object"
+      },
+      "maxItems": 50,
+      "type": "array"
+    },
+    "provenance": {
+      "enum": [
+        "stored_annotations"
+      ],
+      "type": "string"
+    },
+    "truncated": {
+      "description": "The 50-item output cap or bounded stored-segment scan omitted possible references, or stored annotation JSON was unreadable.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "items",
+    "truncated",
+    "provenance"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / source / 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"
+}

addedOutput schema / properties / text_type

Added value: +{
+  "description": "Origin of the selected text, not a guarantee of verbatim speech.",
+  "enum": [
+    "ai_edited_transcript",
+    "ai_summary",
+    "ai_thought"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / total_chars

Added value: +{
+  "description": "UTF-16 code units in the selected text after whitespace normalization, before response truncation; excludes the added ellipsis.",
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Whether the selected text exceeded the 6000-character response limit.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "session_id",
-  "title",
-  "church",
-  "started_at",
-  "url",
-  "source",
-  "transcript"
-]New value: +[
+  "session_id",
+  "title",
+  "church",
+  "started_at",
+  "url",
+  "source",
+  "transcript",
+  "text_type",
+  "truncated",
+  "total_chars",
+  "references"
+]

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / session_id / description

Previous value: -"Exact public sermon session ID returned by search_msza_ai."New value: +"Exact public sermon session ID returned by search_msza_ai or a sermon-listing tool."

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / session_id / description
```
Added value: +"Exact public sermon session ID returned by search_msza_ai."
```
First observedSep 1, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), freeing the description to add genuinely new context: text_type may be AI-edited or fallback rather than verbatim, truncated/total_chars signal completeness, references caps at 50 saved annotations, and those annotations may be machine-generated and incomplete. These data-fidelity caveats are real behavioral disclosure beyond the 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?

Front-loaded with the purpose sentence, then a compact series of caveats. It is not bloated, though the back half reads as a run-on chain of field explanations (text_type, truncated/total_chars, references, selected_section, session) without clear separation, which slightly hurts scanability.

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?

With annotations carrying safety and an output schema present, the description need not restate return structure, yet it still supplies the interpretive nuance (verbatim caveat, annotation reliability, reference cap) an agent needs to use results correctly. Only routing guidance relative to its siblings is absent.

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

Parameters3/5

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

Schema coverage is 100% and there is a single parameter, so the schema already documents session_id fully, including its max length and source tools. The description adds nothing about the parameter beyond the schema, so the baseline 3 for high coverage is correct.

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?

States a specific verb and resource: "Returns public sermon text for an exact session ID in its stored language." An agent can tell this is a lookup-by-ID read tool. However, it never distinguishes itself from the sibling get_transcript, which occupies very similar territory, so differentiation is missing.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of the alternatives. Given siblings like get_transcript, list_recent_sermons, and list_sermons_by_date, an agent has to guess which retrieval path applies. Only the implicit 'you already have a session ID' scenario hints at usage.

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?