Skip to main content
Glama

Find people in the Bible

search_people
Read-onlyIdempotent

Finds people by name or by what is said about them ("king Judah", "prophetess"). Returns ids for get_person.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA name or words about the person, at least 2 characters, e.g. "Tamar", "king of Judah", "prophetess".
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: +"A name or words about the person, at least 2 characters, e.g. \"Tamar\", \"king of Judah\", \"prophetess\"."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety and idempotency, and the description adds useful behavioral context by stating that results are ids intended for get_person. It does not describe matching behavior, result limits, or pagination, but the annotations carry much of the behavioral burden for this simple read-only tool.

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 short sentences with no waste. The core purpose and the key downstream usage are both front-loaded.

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 simple, read-only, two-parameter search tool with full schema coverage, the description plus schema give enough to call it correctly. It also explains the output routing to get_person, though matching semantics and result-size behavior remain unspecified.

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 description coverage is 100%, so both the query and language parameters are already well documented in the schema, including examples and language fallback behavior. The description reinforces that query may be a name or descriptive phrase, but adds little beyond what the schema already provides.

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 gives a specific verb and resource: 'Finds people by name or by what is said about them', with concrete examples ('king Judah', 'prophetess'). It also distinguishes this from generic Bible search by focusing on people and explicitly names the downstream sibling get_person.

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?

It clearly implies the intended workflow by saying 'Returns ids for get_person', so an agent knows this is a lookup step before person retrieval. It stops short of explicitly naming alternatives or when not to use this versus search_bible, but the usage context is clear.

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.