VineVerse — Bible Knowledge Graph

Find places near a location

find_places_near

Read-onlyIdempotent

Biblical places within a radius, nearest first, with the distance in kilometres. Anchor it on a place already in the knowledge base, or on a bare latitude and longitude when you are asking about a modern location that has no document here.

~1,300 places carry coordinates. Many sites are identified only tentatively — check contested and identifications on the place document before treating a position as settled.

total counts everything inside the radius, which a wide one puts well beyond a single page — walk the rest with offset, not by raising the radius.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Anchor latitude, if no place is given.
`lon`	No	Longitude in decimal degrees. Must be given together with `lat`, and instead of `place`.
`limit`	No	How many places to return, nearest first. Defaults to 25, capped at 200.
`place`	No	Anchor place path, e.g. "places/jerusalem"
`offset`	No	For paging; compare with `total` in the response. A wide radius holds far more than one page.
`radius`	No	Kilometres. 50 by default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`total`	Yes
`centre`	Yes
`offset`	Yes
`origin`	No
`licence`	No
`results`	Yes
`radiusKm`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important data behavior: only ~1,300 places have coordinates, many identifications are tentative, and contested/identification fields should be checked before trusting a position. It also explains that total may exceed a single page and warns against widening the radius for paging.

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?

The description is tightly organized into three short paragraphs: what the tool returns, how to choose the anchor, and the important paging caveat. Every sentence contributes new, actionable information without repeating schema descriptions.

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?

Given the schema is complete, output schema is present, and annotations declare the tool read-only and idempotent, the description covers the remaining practical concerns: anchor selection, data quality caveats, and result paging. An agent has enough context to invoke this tool appropriately in both document-based and geographic queries.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds value by framing place versus lat/lon as mutually exclusive anchor strategies, tying offset to total in the response, and reinforcing that a larger radius is not the way to page through a wide result set.

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 states a precise verb and resource: it finds Biblical places within a radius, ordered nearest first with distance in kilometres. This clearly distinguishes it from the sibling tools, which are about entities, scripture, cross references, and general search.

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?

The description explicitly separates the two valid anchor styles: a place already in the knowledge base versus a bare latitude/longitude for modern locations with no document. It gives practical advice about paging with offset instead of raising the radius. It does not name sibling tools as alternatives, but there is no spatial sibling that competes for this task.

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

All VineVerse — Bible Knowledge Graph tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Each tool targets a distinct retrieval task, and the only near-overlaps—get_connections vs find_cross_references, get_stats vs get_status, get_entity vs get_family—are clearly separated by the descriptions. An agent could occasionally hesitate between get_entity and get_family for genealogy, but the purpose statements make the boundary clear.

Naming Consistency4/5

All tool names use clear snake_case verb_noun phrasing, and most are get_* operations. There is a minor stylistic split between get_*, find_*, search_*, and list_*, which gives the set a slightly less uniform feel but is still predictable and readable enough for an agent.

Tool Count4/5

At 16 tools, this is slightly above the typical 3-15 range, but every tool covers a genuinely separate capability: passage lookup, concept search, graph queries, genealogy, interlinear, statistics, and service health. The count is large but reasonable for the breadth of a Bible knowledge graph.

Completeness5/5

For read-only knowledge-graph, the surface is well covered: known-lookup, text and concept search, browsing by collection, cross-references, graph neighborhoods, genealogy, places, interlinear, vocabulary, tags, and every diagnostics. get_stats and get_vocabulary together give an agent a reliable map of the whole domain, so there are no obvious dead ends.

Resources

Need Help?