Skip to main content
Glama

Find stories, themes and prophecies

search_topics
Read-onlyIdempotent

Searches the study material: Bible stories (e.g. "prodigal son"), themes (e.g. "forgiveness"), prophecies and their fulfilment, gospel parallels and timeline events. Returns ids for get_topic.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWords to look for in titles and descriptions, at least 2 characters, e.g. "prodigal son", "forgiveness", "exodus".
languageNoLanguage for names, notes and study content, and for the links to bible.flogvit.com: en (English), nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv (Swedish), fr (French), es (Spanish), fi (Finnish), de (German). Content missing in a language falls back to English. Default: en.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Language for names, notes and study content: en, nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv, fr, es, fi, de. Content missing in a language falls back to English."New value: +"Language for names, notes and study content, and for the links to bible.flogvit.com: en (English), nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv (Swedish), fr (French), es (Spanish), fi (Finnish), de (German). Content missing in a language falls back to English. Default: en."
    • addedInput schema / properties / query / description
      Added value: +"Words to look for in titles and descriptions, at least 2 characters, e.g. \"prodigal son\", \"forgiveness\", \"exodus\"."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the bar is lower, and the description adds the key non-obvious trait: results are identifiers, not content, requiring a follow-up get_topic call. It omits result limits, ranking, and match semantics (fuzzy vs. substring), which an agent would want to know for query construction.

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, no filler, and the searchable content categories are front-loaded before the return-value note. Every clause carries information an agent needs.

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?

For a two-parameter, read-only search tool with full schema coverage and no output schema, the description supplies what the schema cannot: the content domain searched and the fact that the return value is ids for get_topic. Nothing essential to 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 coverage is 100%, with the query format, minimum length, and full language enum with English fallback all documented in the schema. The description's examples echo the schema's own examples rather than adding constraint or format details, so the 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?

States a specific verb (searches) and a precisely enumerated resource: Bible stories, themes, prophecies and fulfilments, gospel parallels, timeline events. The concrete example queries ("prodigal son", "forgiveness") make the scope unambiguous against text-search siblings like search_bible, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The content categories function as use-case triggers, and "Returns ids for get_topic" signals the intended search-then-fetch workflow with a named sibling. It does not state when to prefer a different search tool (search_bible, search_people) or what to do if nothing matches.

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.