Skip to main content
Glama

msza.ai — Polish Catholic Sermons ✝

List the latest public sermons

list_recent_sermons
Read-onlyIdempotent

Returns up to 10 latest public msza.ai sermons in reverse chronological order, optionally limited to one church. This bounded, non-paginated listing contains compact metadata and excerpts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recent_sermons"
  }
}

Input Schema

NameRequiredDescriptionDefault
camera_idNoOptional stable public church profile ID. Omit it to list recent sermons from all churches.

Output Schema

NameRequiredDescriptionDefault
scopeYes
maximumYes
sermonsYes
returnedYes
camera_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral facts the annotations do not: the 10-item cap, that it is non-paginated, the sort order, and that results are compact metadata plus excerpts rather than full content.

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?

Two sentences, front-loaded with the resource and the bound, then the optional filter. No filler, no repetition of the title.

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?

A one-optional-parameter read tool with an output schema and rich annotations needs little more; the description supplies the cap, ordering, non-pagination, and payload shape. Everything required to call it correctly is present.

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 single parameter is already fully documented in the schema, including the 'omit to list from all churches' behavior. The description's 'optionally limited to one church' merely restates that, and notably avoids explaining the church/camera_id naming, adding no new syntax or semantics. Baseline 3 applies.

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?

States a specific verb (returns/lists) and resource (public msza.ai sermons) plus the exact scope: up to 10, reverse chronological, optionally one church. This cleanly separates it from get_sermon (single) and list_sermons_by_date (date-driven), so an agent can pick it without opening the schema.

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?

The word 'latest' plus 'reverse chronological' implies when this tool fits, and 'optionally limited to one church' hints at the filtering choice. But no sibling is named as an alternative and there is no explicit when-not guidance, so usage is only implied.

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