Skip to main content
Glama

CycleCalcs Astronomy

by com.cyclecalcs
OverviewDiscussionsAdmin

Place name to coordinates and timezone

astro_find_place
Read-onlyIdempotent

Resolve a place name to coordinates, region, country, IANA timezone and a stable place_id, or reverse-look-up the nearest places to a lat/lon. Results are GeoNames data (CC BY 4.0); the response carries the required credit in its attribution field, which must be preserved when results are shown. Note the other tools accept a place argument directly, so this is only needed to disambiguate a name, filter by country, or reverse-geocode.

Input Schema

NameRequiredDescriptionDefault
idNoA place_id from an earlier result, to fetch that exact place.
latNoLatitude in decimal degrees, north positive. Send lat and lon together.
lonNoLongitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together.
limitNoMaximum matches to return. Default 5.
queryNoThe place NAME to search for, one to three words, e.g. "Springfield" or "Springfield,US". Never a question or a sentence: send "Lisbon", not "moon phase tonight in Lisbon".
countryNoTwo-letter ISO country code filter, e.g. "US".

Output Schema

NameRequiredDescriptionDefault
dataYesCoordinates for a place name, or the nearest named places to coordinates.
rightsNoEither unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown.
warningsNoMachine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded.
attributionNoThe credit line to display verbatim when rights is attribution_required.
next_cursorNoPresent only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page.
not_computedNoData this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "required": [
+      "lat",
+      "lon"
+    ]
+  }
+]
    • changedInput schema / properties / limit / maximum
      Previous value: -20New value: +25
    • changedInput schema / properties / query / description
      Previous value: -"Place name to search for, e.g. \"Springfield\"."New value: +"The place NAME to search for, one to three words, e.g. \"Springfield\" or \"Springfield,US\". Never a question or a sentence: send \"Lisbon\", not \"moon phase tonight in Lisbon\"."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The MCP projection of a CycleCalcs v2 response: the answer, plus the provenance a caller needs to use it honestly.",
+  "properties": {
+    "attribution": {
+      "description": "The credit line to display verbatim when rights is attribution_required.",
+      "type": "string"
+    },
+    "data": {
+      "additionalProperties": true,
+      "description": "Coordinates for a place name, or the nearest named places to coordinates.",
+      "properties": {
+        "found": {
+          "description": "How many are returned here.",
+          "type": "integer"
+        },
+        "index": {
+          "description": "Which place index answered, and its vintage.",
+          "type": "object"
+        },
+        "matched": {
+          "description": "How many places matched before any limit was applied.",
+          "type": "integer"
+        },
+        "mode": {
+          "description": "Whether this was a name search or a reverse lookup.",
+          "type": "string"
+        },
+        "results": {
+          "description": "Each place with coordinates, country, population and a place_id that other tools accept.",
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "next_cursor": {
+      "description": "Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page.",
+      "type": "string"
+    },
+    "not_computed": {
+      "description": "Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as \"withheld\", never as \"none exists\".",
+      "type": "array"
+    },
+    "rights": {
+      "description": "Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown.",
+      "type": "string"
+    },
+    "warnings": {
+      "description": "Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded.",
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description adds genuinely non-structured context: results are GeoNames data under CC BY 4.0 and the attribution field must be preserved when shown, plus that place_id is stable and reusable in the `id` parameter. No pagination or error behavior mentioned, hence not a 5.

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?

Three sentences, front-loaded with capabilities, then licensing obligation, then the routing note — no filler. The attribution sentence is slightly heavy but carries a real compliance requirement, so it earns its space.

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?

Covers all three invocation modes, the data source and licensing obligation, the stable-id round-trip, and when to prefer siblings. With a full output schema and full annotation coverage, nothing an agent needs to call 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% with clear per-field descriptions (including the anyOf-required groups), so baseline is 3. The description adds mode-level semantics beyond the schema: it explains that the three shapes are name-lookup, id-fetch, and reverse geocode, and that the name lookup is what you need to disambiguate or country-filter.

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?

States a specific verb+resource ('Resolve a place name to coordinates, region, country, IANA timezone and a stable place_id') and covers the reverse direction ('reverse-look-up the nearest places to a lat/lon'), i.e. all three input modes. It also names the sibling class ('the other tools accept a place argument directly'), so an agent can tell this apart from astro_rise_set, astro_positions, etc.

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?

Explicit when-not guidance: this tool 'is only needed to disambiguate a name, filter by country, or reverse-geocode', implying other tools take a place directly. That is the exact routing decision an agent faces against the ten sibling tools.

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

All CycleCalcs Astronomy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources