Skip to main content
Glama

Sermon Registry

List topics

list_topics
Read-onlyIdempotent

Every sermon topic id with its name and group, for use with search_sermons.

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_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds value beyond them by disclosing the return fields (id, name, group) and implying full enumeration ('Every'), which matters because there is no output schema. It says nothing about ordering or list size, a minor omission for a static taxonomy.

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?

One short sentence, front-loaded with the returned data and ending on the tool it feeds. Every clause earns its place, with no padding or restatement 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?

For a zero-argument, read-only enumeration with no output schema, the description covers what is returned and why. Only secondary details — ordering, approximate list size, whether the taxonomy changes — are left out, which is acceptable at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and no compensation is needed. The description correctly avoids inventing parameter behavior and instead spends its words on what the return set contains.

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 states the resource (sermon topics) and the exact payload returned — every topic id with its name and group — which tells an agent precisely what it gets. It lacks an explicit verb, but 'Every ... topic id with its name and group' plus the cross-reference to search_sermons makes the intent unambiguous and distinguishable from get_sermon or find_churches.

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?

It states the downstream purpose ('for use with search_sermons'), which implies the call-first-to-discover-topic-ids workflow. It offers no explicit when-not guidance and never says the tool takes no arguments, so an agent must infer that this is a static enumeration rather than a filtered query.

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