Skip to main content
Glama

Astral Code

Find a birth location

find_birth_locations
Read-onlyIdempotent

Find city coordinates and IANA timezone for a birth chart. Ask the user to choose if multiple places match. Do not invent coordinates or silently choose another city.

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": "find_birth_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
localeNoConversation language. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description usefully adds anti-hallucination and disambiguation policy, but says nothing about result ordering, maximum matches returned, or what happens on a zero-match query.

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?

Three short sentences, front-loaded with the capability, then the disambiguation rule, then the failure-mode constraint. No filler or restated title text.

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?

With no output schema, the description correctly discloses the two returned values (coordinates and timezone). For a two-parameter lookup this is close to complete; only the no-match outcome and query format expectations leave an agent guessing.

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 50%: locale is documented in-schema while query has only length bounds. The description implies query is a place name and that it can be ambiguous, adding some meaning, but never clarifies accepted formats (city only vs. city+region+country) or how locale affects matching.

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?

States a specific verb and resource ('Find city coordinates and IANA timezone') and scopes it to 'a birth chart', which positions it as the geocoding step before calculate_birth_chart. It does not explicitly name a sibling to avoid, so it falls short of full sibling differentiation.

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?

Provides concrete operating guidance: ask the user to disambiguate when multiple places match, and never invent coordinates or silently pick a different city. It stops short of naming when to prefer this over the other tools, but the lookup-versus-calculation split against calculate_birth_chart is reasonably clear from context.

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.

Resources