Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Describe coordinates

tl_reverse_geocode
Read-onlyIdempotent

Converts latitude and longitude coordinates into province, city, and neighbourhood details so you can determine the correct city for shipping rules.

Instructions

Describe coordinates as an address with province, city and neighbourhood.

Use to get the city for shipping rules.

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": {
      "lat": "<lat>",
      "long": "<long>"
    },
    "name": "tl_reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, e.g. 35.7575.
longYesLongitude, e.g. 51.4106.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude (Iran: ~25 to ~40), e.g. 35.7575."New value: +"Latitude, e.g. 35.7575."
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • changedInput schema / properties / long / description
      Previous value: -"Longitude (Iran: ~44 to ~63), e.g. 51.4106."New value: +"Longitude, e.g. 51.4106."
    • removedInput schema / properties / long / title
      Removed value: -"Long"
    • removedInput schema / title
      Removed value: -"tl_reverse_geocodeArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_reverse_geocodeDictOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and open-world, so the safety profile is clear. The description adds that the output is an address with province, city, and neighbourhood, but does not cover failure behavior for out-of-range coordinates or other operational constraints.

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?

Two short sentences, front-loaded with the core operation. The second sentence adds a useful practical context without redundant wording.

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?

For a simple two-parameter read-only tool, the description gives enough output detail by naming province, city, and neighbourhood. It could mention coordinate restrictions or a caveat about coverage, but annotations and the schema fill most remaining gaps.

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%, so the parameters are already documented with types, ranges, and examples. The description does not add meaning about the lat/long inputs beyond what the schema provides, which is appropriate given the coverage.

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?

The description states a specific verb and resource: describing coordinates as an address with province, city, and neighbourhood. It clearly distinguishes reverse geocoding from search-oriented siblings, though it does not explicitly name the most likely alternative, tl_find_location.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one concrete use case: getting the city for shipping rules. However, it does not explain when not to use this tool or name alternatives such as tl_find_location, leaving the agent to infer the selection context.

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