msza.ai — Polish Catholic Sermons ✝

Get a public prayer

get_prayer

Read-onlyIdempotent

Returns one saved public prayer-book item: prayer, song, or fixed liturgical text. Bare prayer IDs and namespaced song: and standard: IDs are supported. kind, text_status, and truncated describe content availability; a song can contain only a first line or metadata. rights_note records provenance rather than permission. Text is stored content without generation or network retrieval.

Input Schema

Name	Required	Description	Default
`prayer_id`	Yes	Existing bare prayer ID, or exact namespaced prayer_id/item_id (song:<id> or standard:<id>) returned by search or transcript/sermon references.

Output Schema

Name	Required	Description	Default
`url`	Yes
`kind`	Yes
`note`	Yes
`text`	Yes
`type`	Yes
`title`	Yes
`item_id`	Yes
`prayer_id`	Yes
`truncated`	Yes
`source_url`	Yes
`rights_note`	Yes
`text_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 16, 2026

changedInput schema / properties / prayer_id / description

Previous value: -"Exact prayer sourceId returned by search_msza_ai, or id of a prayer in get_sermon.references."New value: +"Existing bare prayer ID, or exact namespaced prayer_id/item_id (song:<id> or standard:<id>) returned by search or transcript/sermon references."

changedInput schema / properties / prayer_id / maxLength
```
Previous value: -160New value: +200
```
addedOutput schema / properties / item_id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / kind

Added value: +{
+  "enum": [
+    "prayer",
+    "song",
+    "liturgical"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / rights_note

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

addedOutput schema / properties / text_status

Added value: +{
+  "enum": [
+    "stored_text",
+    "first_line",
+    "unavailable"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / type / enum

Previous value: -[
-  "prayer"
-]New value: +[
+  "prayer",
+  "song",
+  "liturgical"
+]

changedOutput schema / required

Previous value: -[
-  "prayer_id",
-  "title",
-  "type",
-  "text",
-  "note",
-  "source_url",
-  "url"
-]New value: +[
+  "prayer_id",
+  "item_id",
+  "title",
+  "type",
+  "kind",
+  "text",
+  "text_status",
+  "truncated",
+  "note",
+  "rights_note",
+  "source_url",
+  "url"
+]

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / prayer_id / description

Previous value: -"Exact prayer sourceId returned by search_msza_ai."New value: +"Exact prayer sourceId returned by search_msza_ai, or id of a prayer in get_sermon.references."

AddedSep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, yet the description adds real value beyond them: content may be partial (a song may expose only a first line or metadata), rights_note is provenance rather than a permission grant, and text is stored rather than generated or fetched. These are behavioral caveats an agent would otherwise get wrong.

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 tight sentences, front-loaded with what is returned before the ID and content-status caveats. The final sentence about stored versus generated text is near-redundant with openWorldHint=false but still clarifies the distinction, so it earns its place only marginally.

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 an output schema present and rich annotations, the description need not explain return values; it focuses on the non-obvious parts (partial content, rights semantics, ID namespacing). It could still state when an ID is unavailable or what happens on a missing item, which is the one remaining gap.

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 description coverage is 100% and the single parameter already documents the bare and namespaced (song:<id>, standard:<id>) ID forms. The description restates the same ID forms without adding syntax, precedence, or error-handling detail, so it sits at the high-coverage baseline.

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 concrete verb and resource and, unusually, enumerates the three content types the resource can hold (prayer, song, fixed liturgical text), which prevents an agent from assuming this is prayer-only. It does not explicitly contrast itself with any sibling tool, but the resource is distinct enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer it needs an ID obtained from search or a transcript/sermon reference, but the description never says when to call this versus get_sermon, get_transcript, or search tools, and gives no exclusions or preconditions.

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?