Skip to main content
Glama

msza.ai — Polish Catholic Sermons ✝

Search public msza.ai sources

search_msza_ai
Read-onlyIdempotent

Searches public, predominantly Polish-language msza.ai sermons, sermon studies, Bible passages, prayers, songs, people, and places by topic, keyword, and relevance. Results retain stored source language and contain candidate matches, stable source IDs, citation labels, short excerpts, dates, and links. Date and church filters apply to sermon records. Priest names are unavailable.

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": {
      "query": "<query>"
    },
    "name": "search_msza_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of compact source results to return.
queryYesFocused Polish retrieval query for a topical request. For another user language, translate only topical terms into Polish while preserving proper names, exact IDs, Bible references, and supplied filters.
date_toNoOptional last Warsaw calendar day of an absolute archive period, inclusive.
weekdayNoOptional Warsaw weekday filter: Sunday=0, Monday=1, ..., Saturday=6.
camera_idNoOptional stable church profile ID. When supplied, only public sermons from that church are searched.
date_fromNoOptional first Warsaw calendar day of an absolute archive period, inclusive.
days_backNoOptional rolling calendar-day window ending today, for example 7 or 28. Omit when using date_from or date_to.
content_typesNoOptional 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

NameRequiredDescriptionDefault
queryYes
filtersYes
sourcesYes
retrievalNo
archiveCapabilitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Focused natural-language search query in Polish or English."New value: +"Focused Polish retrieval query for a topical request. For another user language, translate only topical terms into Polish while preserving proper names, exact IDs, Bible references, and supplied filters."
  2. Changed2 schema fields changed
    • 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"
      +}
  3. Changed6 schema fields changed
    • 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"
      +}
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of compact source results to return."
  6. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses real behavioral traits: results retain stored source language, return candidate matches with stable IDs, citation labels, excerpts, dates and links, filters are scoped only to sermon records, and priest names are unavailable. These are non-obvious constraints an agent could not infer from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: scope first, then result shape, then filter/limitation caveats. No filler and the most important framing (what is searched) is front-loaded.

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?

With an output schema present and 100% parameter coverage, the description covers the remaining gaps an agent needs: which sources are searched, that results are candidate matches with citations, that date/church filters only touch sermons, and that priest names are unavailable. Nothing required for correct invocation is missing.

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%, so the schema already documents all eight parameters, including content_types semantics and date filter scoping. The description echoes the sermon-only filter constraint and the priest-name limitation but adds little syntax or format detail beyond what the schema provides, so baseline 3 applies.

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?

The description gives a specific verb and resource set: searching public msza.ai sermons, studies, Bible passages, prayers, songs, people and places by topic, keyword and relevance. That distinguishes it from the get_*/list_* siblings, which are ID- or listing-oriented, though no sibling is named explicitly.

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 implied by 'by topic, keyword, and relevance' (discovery-style lookup) and by the note that date/church filters apply to sermons. However, there is no explicit when-to-use guidance versus get_sermon, get_person, or list_sermons_by_date, and no statement of when this tool is the wrong choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources