Skip to main content
Glama

lookup_name

Read-onlyIdempotent

Retrieve relationships and connections for any biblical person, place, or thing to deepen thematic Bible study.

Instructions

USE THIS when any biblical person, place, or thing is mentioned.

This is your PRIMARY TOOL for thematic linking across the Bible. The database contains 4,000+ biblical persons and 1,000+ places with rich relationship data.

RELATIONSHIP DATA ENABLES THEMATIC CONNECTIONS:

  • Parents: Trace lineages backward (e.g., David → Jesse → Obed → Boaz → Salmon)

  • Children: Trace lineages forward (e.g., Abraham → Isaac → Jacob → 12 tribes)

  • Siblings: Connect related narratives (e.g., Moses ↔ Aaron ↔ Miriam)

  • Spouse: Connect family narratives (e.g., Ruth → Boaz → David's lineage)

THEMATIC LINKING EXAMPLES:

  1. Messianic lineage: lookup Abraham → David → Solomon → ... → Joseph/Mary

  2. Priesthood lineage: lookup Aaron → Eleazar → Phinehas → ... → Zadok

  3. Geographic connections: lookup Bethlehem for its role in Ruth, David, and Jesus narratives

  4. Prophecy fulfillment: trace how places mentioned in OT prophecy appear in NT

When answering questions about biblical characters or places, ALWAYS check their relationships to find connections that enrich your answer with biblical context.

This grounds character discussions in the actual biblical data rather than just training recall.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName to look up (e.g., 'David', 'Jerusalem', 'Abraham')
typeNoFilter by type. Omit to search all types.
Behavior5/5

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

Annotations indicate readOnly, destructive=false, idempotent. Description adds significant detail about the database size, relationship data (parents, children, siblings, spouse), and thematic linking capabilities, enhancing understanding beyond annotations.

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?

Well-structured with headings, bullet points, and examples. Front-loaded with an imperative. However, it is somewhat verbose and could be more concise without losing value.

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?

Given no output schema, the description explains the relationship data and gives thematic linking examples, providing sufficient context for an agent to use the tool effectively. Could be more precise about the return format.

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 name (string) and type (enum). The description does not add additional meaning beyond what the schema provides; it only repeats the parameter purposes indirectly. Baseline 3 is appropriate.

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?

Clearly states the tool is for looking up biblical persons, places, or things, and emphasizes thematic linking. The description positions it as the primary tool for such lookups with specific examples.

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?

Starts with explicit 'USE THIS when' and provides clear context with examples of when to use it for thematic linking. However, it does not explicitly mention when to use alternative sibling tools like explore_genealogy or explore_place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djayatillake/studybible-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server