Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Find location

tl_find_location
Read-onlyIdempotent

Converts an address or landmark into coordinates, province, and city so you can determine shipping availability.

Instructions

Turn an address or landmark into coordinates with its province and city.

Shipping depends on the city (tl_store_info topic=shipping).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax places to return.
queryYesAddress or landmark, Persian works best, e.g. 'میدان ونک'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • changedInput schema / properties / query / description
      Previous value: -"Address, street or landmark, Persian works best, e.g. 'میدان ونک' or 'شیراز خیابان زند'."New value: +"Address or landmark, Persian works best, e.g. 'میدان ونک'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"tl_find_locationArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_find_locationDictOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent, open-world lookup. The description adds value beyond them by disclosing the shape of the result (coordinates plus province and city), which matters because no output schema exists. It does not warn that geocoding is approximate or that multiple places may match, which is the main behavioral gap for an open-world lookup.

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 definition consists of two compact sentences front-loaded with the core operation, and the second sentence is a justification, not filler. The parenthetical '(tl_store_info topic=shipping)' is terse but functional; a slightly clearer phrasing of the dependency would be the only improvement.

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 two-parameter, read-only lookup whose schema is fully documented and whose annotations cover the safety profile, the description is nearly sufficient, mainly because it states what the tool returns. It omits any statement about the response format or how ambiguous matches are resolved, which is the one remaining gap.

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 100%, so both `query` and `limit` are already documented, including the note that Persian input works best. The description adds no further meaning about query syntax or about how `limit` interacts with ambiguous matches. A baseline 3 is appropriate when the schema carries the parameter load.

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+resource: turning an address or landmark into coordinates, and it also names the returned fields (province and city). This implicitly distinguishes it from tl_reverse_geocode, which does the opposite; however, the description never explicitly compares the two.

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?

The second sentence gives concrete usage context: the tool is needed when shipping costs depend on the city, and it routes the agent to tl_store_info topic=shipping for that follow-up. It does not give any when-not-use guidance, such as when to use tl_reverse_geocode or how to handle an ambiguous address.

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