Skip to main content
Glama

Shprd Bible

Search the Bible

search_bible
Read-onlyIdempotent

Use this when the user wants to find verses by words or a phrase in the World English Bible, for example "where does it say 'do not be anxious'" or "verses about shepherd in Psalms". Matches whole words and word beginnings of up to 8 distinct words (words under 2 letters and extras are ignored); every word must appear, otherwise verses with most of the words are returned and marked some_words. Results are WEB wording only, so a phrase from another translation may not match. Returns up to limit verses and the total count. Do not use it to read a known passage (use get_bible_passage).

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

Input Schema

NameRequiredDescriptionDefault
bookNoOptional book to search within, e.g. "Psalms" or "1 John".
limitNoNumber of verses to return (1-25, default 10).
queryYesWords or a phrase to find, e.g. "love your enemies".

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes
returnedYes
matchTypeYes
attributionYes
translationYes
totalMatchesYes
termsSearchedYesThe distinct words actually searched (at most 8, each 2+ letters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world semantics, and the description still adds substantial behavior beyond them: whole-word and word-prefix matching, an 8-distinct-word cap, that sub-2-letter words are ignored, that non-matching conjunctions fall back to a ranked result flagged some_words, and that only WEB wording matches. That is exactly the kind of non-obvious matching semantics an agent cannot get from the structured fields.

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?

Front-loaded with usage and an example, then matching rules, then the boundary condition and the anti-pattern. Dense and largely waste-free, though the middle parenthetical packs several rules into one sentence and could be split for readability.

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?

Although an output schema exists, the description nonetheless states the practical return shape (up to `limit` verses plus total count), and it discloses the translation constraint and partial-match behavior that could otherwise mislead an agent interpreting results. Nothing material is missing for a 3-parameter search tool.

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 100%, so the baseline is 3; the description earns above that by documenting query semantics the schema does not (word limits, ignored tokens, some_words fallback) and how book scopes the search. It does not restate limit bounds, but the schema already covers those.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("find verses by words or a phrase in the World English Bible") and immediately contrasts with a named sibling ("Do not use it to read a known passage (use get_bible_passage)"), so the agent can select among siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives concrete when-to-use examples ("where does it say 'do not be anxious'", "verses about shepherd in Psalms") plus an explicit negative case that routes to get_bible_passage. Both the trigger and the exclusion are stated, not implied.

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