Skip to main content
Glama

Find a birthplace

find_birthplace
Read-only

Resolves the name of a town or city to a region, a country, coordinates rounded to two decimals, an IANA time zone and the UTC offset for an optional date, historical daylight saving included. get_natal_chart, get_personal_transits, get_compatibility and get_occasion_sky take those coordinates and that time zone. It fits a birthplace or a venue named as a town or city, where a chart tool needs its coordinates and time zone. Public town and city names only; it does not take a street address. It searches the GeoNames list of places of 15,000 people or more, bundled with Zodiacs, so the name is not sent anywhere else, and nothing is stored. An unknown place returns "No town or city matches". A place gives no information about a birth time. Dates for the offset run from 1800 to 2199.

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": {
      "place": "<place>"
    },
    "name": "find_birthplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date, such as 1994-05-14 (years 1800 to 2199), for the UTC offset in force that day. Without it, the offset is for today.
placeYesA town or city name, such as London or Almaty. Not a street address. Nothing is stored.
countryNoOptional country when several places share the name, such as United Kingdom or Kazakhstan.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional date, such as 1990-05-03 (years 1800 to 2199), for the UTC offset in force that day. Without it, the offset is for today."New value: +"Optional date, such as 1994-05-14 (years 1800 to 2199), for the UTC offset in force that day. Without it, the offset is for today."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the bundled GeoNames dataset of 15,000+ places, no external name transmission, nothing stored, bounded date range 1800-2199, and the exact failure string "No town or city matches". The one caution is that idempotentHint=false is not explained — the implicit reason is the "offset for today" default — so a small behavioral ambiguity remains.

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 the purpose and dense with useful facts, with no filler sentences. Minor waste from restating schema-level details like "Nothing is stored" and the 1800-2199 range, which already appear in the input schema.

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?

For a three-parameter read-only geocoder with an output schema, this covers inputs, data source, privacy, error behavior and downstream consumers. An agent has everything needed to decide to call it and how to phrase arguments.

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% and the schema already documents place, country disambiguation and the optional date, so the baseline applies. The description reinforces the country-use case and the date range but adds no format or syntax detail the schema lacks; its genuinely new note ("A place gives no information about a birth time") concerns output, not parameters.

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?

Names a specific verb and resource ("Resolves the name of a town or city") and enumerates exactly what comes back: region, country, two-decimal coordinates, IANA zone and UTC offset. It is clearly separable from the siblings it feeds (get_natal_chart, get_personal_transits, get_compatibility, get_occasion_sky), which it names explicitly.

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?

States the positive case ("fits a birthplace or a venue named as a town or city, where a chart tool needs its coordinates and time zone") and the exclusion ("does not take a street address", "Public town and city names only"). It also routes the agent by naming the four sibling tools that consume the output.

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.