Skip to main content
Glama

La Iglesia Católica de los Agentes de AI

Bible search

bible_search
Read-onlyIdempotent

{"use_when":{"en":"Use when someone remembers the words of a Bible verse but not where it is.","es":"Úsala cuando recuerden las palabras de un versículo pero no la cita."},"what":{"en":"Simple word/phrase search (case- and accent-insensitive), max 20 results. To keep it fast it searches ONE book if book is given (e.g. ROM); otherwise ONLY the four Gospels (MAT MRK LUK JHN) and the Psalms (PSA).","es":"Búsqueda simple; sin book busca solo en Evangelios y Salmos."}}

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

Input Schema

NameRequiredDescriptionDefault
bookNoOptional book id to search in (e.g. GEN, ROM, SIR)
langNoLanguage / Idioma: es (default), en, ites
bibleNoBible id (e.g. drc, webc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one.
limitNo
queryYesWord or phrase / Palabra o frase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / bible / description
      Previous value: -"Bible id (e.g. drc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one."New value: +"Bible id (e.g. drc, webc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses a non-obvious and consequential constraint: with `book` it searches ONE book, and without `book` it searches ONLY the four Gospels and Psalms – a major recall limitation an agent could not infer from the schema. It also states case/accent insensitivity and the 20-result cap, so the agent knows both the matching behavior and the scope ceiling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two-part structure (use_when, then what) is well front-loaded and each sentence carries information. The cost is the parallel Spanish duplicate, which roughly doubles the token footprint for an agent that only needs one language.

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 5-parameter, read-only search tool with no output schema, the definition covers the essential decision inputs: when to reach for it and the corpus it actually searches. The default `bible` resolution and `limit` default are already in the schema, so their absence in the description is not a meaningful gap.

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?

Schema coverage is 80% and the `book` parameter already has a description, yet the description adds real meaning the schema lacks: that supplying `book` narrows the corpus to a single book while omitting it narrows it to the Gospels and Psalms. That is parameter behavior, not just a restated field label. It adds nothing for `lang`, `bible`, or `limit`, which the schema already documents.

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 'what' block states a specific verb and resource ('Simple word/phrase search') over Bible verse text, and the 'use_when' block pins the scenario to 'remembers the words of a Bible verse but not where it is' – which implicitly separates it from the citation-lookup sibling bible_passage. It stops short of naming that sibling, so the differentiation is inferable rather than explicit.

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?

'Use when someone remembers the words of a Bible verse but not where it is' is a genuine when-to-use trigger with a clear scenario boundary. There is no explicit when-NOT-to-use clause or named alternative, which keeps it out of the top band, but an agent will know the right context for this tool.

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