Skip to main content
Glama

Sermon Registry

Search sermons

search_sermons
Read-onlyIdempotent

Search published sermons by keywords, topics, Bible book, preacher, church or language. Returns titles, preachers, churches, dates, topics, main Bible passages and links; never transcripts.

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": "search_sermons"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoWords to search for in sermon titles, summaries and takeaways.
bookIdNoA Bible book id such as ROM, JHN or PSA.
churchNoA church's name.
topicsNoTopic ids from list_topics; a sermon must have all of them.
languageNoSermons available to read in this language.
pageSizeNo
preacherNoA preacher's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description is free to add genuine value: it discloses that only published sermons are searched and that results never include transcripts, which tells the agent it must fetch content elsewhere. It does not mention pagination limits (10 pages, page size 10) or result ordering.

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 densely packed sentences with no filler: the searchable surface comes first, then the return shape and its one important exclusion. Nothing is repeated and nothing could be cut without losing information.

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 8 optional parameters and no output schema, the description does the right work by summarizing the returned fields so the agent knows what it gets back without a schema. The remaining gap is guidance on combining filters and paging, which the schema covers only partially.

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 75%, so the schema already documents most parameters in detail, including the topics enum and its all-must-match semantics. The description restates which facets are searchable but adds no format, combination, or paging detail beyond the schema, making the baseline 3 appropriate.

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 names a specific verb and resource ("Search published sermons") and enumerates the six facets that can be searched, so an agent immediately knows what the tool does and that its scope is limited to published content. It does not explicitly contrast with get_sermon or list_topics, leaving sibling differentiation to inference.

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 the facet list — search when you know something about the sermon's title, topic, book, preacher, church or language — but there is no explicit statement of when to prefer this over get_sermon or how to chain it with list_topics for topic ids. No exclusions or prerequisites are stated.

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