Skip to main content
Glama

A person in the Bible

get_person
Read-onlyIdempotent

One person: summary, family, related people and key events with the passages where they happen.

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": {
      "id": "<id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson id from search_people or get_chapter_study, e.g. "tamar-juda".
mappingNoVerse numbering to give the verse references in: a mapping id from list_verse_mappings, e.g. "english_kj" (King James) or "dnb2024_nb", or a short name such as "kjv". Default: osnb, the site's own numbering.
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 / mapping
      Added value: +{
      +  "description": "Verse numbering to give the verse references in: a mapping id from list_verse_mappings, e.g. \"english_kj\" (King James) or \"dnb2024_nb\", or a short name such as \"kjv\". Default: osnb, the site's own numbering.",
      +  "minLength": 2,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful content-level transparency by listing what the response contains (family, related people, key events with passages), but it does not mention error behavior for invalid ids, response size, or whether this is a full biography versus a summary.

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?

It is a single compact sentence that front-loads the resource and enumerates return content without filler. It is efficient, though its terseness leaves some gaps that a slightly longer description could close.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should explain return values more fully; it lists content categories but not structure or depth. Combined with the absence of usage guidance, this is adequate but incomplete for a detail-fetch tool.

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 the schema already documents id, mapping, and language thoroughly, including examples and defaults. The description adds no parameter-specific meaning beyond what the schema provides, so baseline 3 is appropriate.

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 description names a specific resource ('One person') and enumerates the content returned: summary, family, related people, key events, and passages. It is distinguishable from search_people, which is a search rather than a detail fetch, though the description itself does not explicitly contrast with that sibling or use an explicit retrieval verb.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of alternatives, and no prerequisites. The schema notes that the id comes from search_people or get_chapter_study, but the description carries none of that routing guidance on its own.

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.