Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_search_location

Read-onlyIdempotent

Search for a place by name to get its latitude, longitude, and IANA timezone for use in astrology tool inputs. Returns up to 10 matches, largest population first, for user confirmation.

Instructions

Search for a place by name and get its coordinates and timezone, for the place, lat, lon and tzone inputs of the other tools.

Returns up to 10 matches, largest population first, each with place_id, name, full_name (e.g. 'Patna, Bihar, India'), country, admin1 (state or region), latitude, longitude, timezone (IANA name, e.g. Asia/Kolkata), timezone_value (UTC offset in hours) and population. Matching is by name prefix. When several places match, confirm with the user which one is meant.

timezone_value is the zone's offset today. For a birth date in a zone with summer time (most of the Americas and Europe) or with historical changes, the offset on that date can differ (New York is -5 in winter and -4 in summer), so work out the offset for the birth date from the IANA timezone before passing it as tzone.

Place data (c) GeoNames (geonames.org), CC BY 4.0: keep the attribution when showing results.

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

Input Schema

NameRequiredDescriptionDefault
placeYesPlace name to search for, at least 3 characters (e.g. 'Patna', 'New York')

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag the tool as read-only, idempotent, open-world and non-destructive, and the description adds substantially beyond that: a 10-result cap, population-descending ordering, prefix matching, the full field list, and the caveat that timezone_value is today's offset rather than the offset on a birth date. The GeoNames CC BY 4.0 attribution requirement is also disclosed, which the agent must otherwise violate unknowingly.

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 purpose, then results shape, then disambiguation, then the DST caveat and attribution. Every block earns its place, though the timezone/DST paragraph is dense and could be tightened without losing the warning.

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 one-parameter lookup with an output schema, the description covers result ordering, result cap, field semantics, the most likely source of downstream error (DST offsets), and the legal attribution requirement. Nothing an agent needs in order to call and interpret this correctly is missing.

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?

Schema coverage is 100% and the single parameter is well documented in the schema, but the description still adds meaning by specifying that matching is by name prefix rather than substring or fuzzy matching, and by giving example place inputs that satisfy the 3-character minimum.

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 first sentence names a specific verb and resource ('Search for a place by name') plus the concrete outputs (coordinates and timezone), and states the downstream purpose: supplying the place, lat, lon and tzone inputs of the other tools. That immediately separates it from the sibling astrology tools, which none of them do geocoding.

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?

It explains the calling context ('for the place, lat, lon and tzone inputs of the other tools') and gives a concrete disambiguation rule: when several places match, confirm with the user which one is meant. It stops short of naming alternatives or exclusion cases, but no sibling appears to compete for this job.

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

Deploy Server

Other Tools