Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find location

tl_find_location
Read-onlyIdempotent

Convert an address or landmark into coordinates, province, and city to determine shipping city or find the nearest branch.

Instructions

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

Use to find an address's city (shipping depends on it, see tl_store_info topic=shipping) or the nearest branch.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered. The description adds value the structured fields cannot: it discloses the return contents (coordinates, province, city) in the absence of an output schema, and flags the shipping dependency. It omits ambiguity handling (multiple matches) and any rate-limit context.

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 transformation, then the use cases. No filler, every clause carries information.

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 with full schema coverage, the description covers purpose, use cases, and return contents. It does not address what happens when the query is ambiguous or when multiple places match the default limit of 5, a minor gap given no output schema exists.

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%: both 'query' (Persian-address example) and 'limit' (range, default) are already documented in the schema. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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-and-resource transformation (address/landmark -> coordinates, province, city), which is a different operation from the inverse geocoding in the sibling list. An agent can tell it apart from tl_reverse_geocode without reading 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 Guidelines4/5

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

Names two concrete use cases (resolving an address's city for shipping, finding the nearest branch) and cross-references tl_store_info topic=shipping. It stops short of an explicit exclusion or forward-reference to tl_reverse_geocode for the opposite direction, so routing is clear but not fully disambiguated.

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