Skip to main content
Glama

Aviation & Space Weather Data (Tanod)

geocode

Read-onlyIdempotent

utilpeek: offline geocoding over the GeoNames cities15000 table. For places of a kind nearby use find_places_nearby. Input: either place alone or lat and lon together. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code or a US state code); no match is a 404 place_not_found (not charged). Cities only (no street addresses). Typically under 0.1 s (first call up to 1 s). Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Data: GeoNames (geonames.org) cities15000, CC BY 4.0; credit it when you show or republish it (the attribution field carries the text). Docs: https://tanod.dev/learn/reverse-geocoding-api.html

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoReverse: latitude (-90..90); give lat and lon together, or place.
lonNoReverse: longitude (-180..180); give lat and lon together, or place.
placeNoForward: city name, optionally "City, CC" (ISO country or US state code); give place alone, or lat and lon.

Output Schema

NameRequiredDescriptionDefault
modeNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
queryNo
totalNo
filterNo
resultsNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / lat / default
      Removed value: -null
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / lon / default
      Removed value: -null
    • removedInput schema / properties / lon / title
      Removed value: -"Lon"
    • removedInput schema / properties / place / default
      Removed value: -null
    • removedInput schema / properties / place / title
      Removed value: -"Place"
    • removedInput schema / title
      Removed value: -"geocodeArguments"
    • removedOutput schema / properties / attribution / properties
      Removed value: -{
      -  "changes": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "places": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / results / items
      Removed value: -{
      -  "properties": {
      -    "admin1_code": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "country_code": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "distance_km": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "lat": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "lon": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "matched_on": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "name": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "population": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "timezone": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {
      +      "properties": {
      +        "changes": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "places": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "filter": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "mode": {
      +      "enum": [
      +        "forward",
      +        "reverse",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "query": {
      +      "type": [
      +        "string",
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "admin1_code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "country_code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "distance_km": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "lat": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "lon": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "matched_on": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "population": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "timezone": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), it discloses the failure mode (404 place_not_found), that failures are not charged, expected latency (under 0.1 s, up to 1 s on first call), pricing (USD 0.001), the free tier (10 calls per IP per UTC day), and the data license plus attribution obligation. That is substantial behavioral context an agent could not infer from the structured fields.

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?

The critical routing and input-mode information is front-loaded in the first two sentences, and the remaining detail is compact bullet-like prose. The pricing, free-tier, license, and docs tail makes it denser than strictly necessary for invocation, though each element is genuinely useful.

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?

With an output schema present, the description need not explain return values, and it covers everything else an agent needs: input modes, matching constraints, error behavior, cost, latency, and attribution requirements. Nothing material is missing for correct invocation.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not carry: the 15,000-population match threshold, the requirement that `place` resolve to a real city entry, and the fact that lat/lon is the reverse path. It largely restates the 'City, CC' format already in the schema, which keeps it from a 5.

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 opens with a specific verb and resource: 'offline geocoding over the GeoNames cities15000 table.' It immediately scopes the capability (cities of 15,000+ people, no street addresses) and names the sibling tool it is not, so an agent can distinguish it from find_places_nearby without opening either schema.

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?

It gives explicit routing guidance ('For places of a kind nearby use find_places_nearby') and defines the two mutually exclusive invocation modes: `place` alone, or `lat` and `lon` together. It also states an exclusion ('Cities only (no street addresses)') so the agent knows when this tool is the wrong choice.

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.