Skip to main content
Glama

Sermon Registry

Get a sermon

get_sermon
Read-onlyIdempotent

One published sermon's details: Sermon Registry's summary and takeaways, preacher, church, date, topics, Bible passages and links. No transcript text.

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": {
      "slug": "<slug>"
    },
    "name": "get_sermon"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe sermon's slug: the last part of its sermonregistry.com URL.

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is scope: only published sermons, and explicitly 'No transcript text', which pre-empts a common wrong expectation. It does not describe behavior when a slug is unknown (error vs empty), a minor gap.

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 tight sentences: the resource and its returned fields first, then the negative constraint. Every clause carries information, with no filler or repetition of the title.

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 no output schema, the description correctly shoulders the burden by enumerating returned fields, which is sufficient for a single-parameter read. Only failure/not-found behavior is unspecified, which is minor for this complexity.

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 the slug parameter is fully documented, including the URL-suffix semantics and pattern. The description adds no further meaning about the parameter, so the baseline of 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?

States a specific verb-like operation (fetch one published sermon's details) and enumerates the returned fields: summary, takeaways, preacher, church, date, topics, passages, links. The singular 'One published sermon' distinguishes it from search_sermons, though no sibling is named.

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 required slug parameter signals a lookup-by-identifier pattern. There is no explicit guidance such as 'use search_sermons first to obtain a slug' or when to prefer this over searching, leaving the agent to infer the flow.

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