Skip to main content
Glama

Visibility Genies

Find a location code

find_location
Read-only

Looks up the numeric location code a place has, instead of guessing one. Countries are the markets keyword, domain and backlink tools take as locationCode; with countryCode, cities and regions of that country are looked up too, for search results and rank trackers. A misspelled name returns the nearest names. Free: it reads the saved location lists and never fetches anything; a country whose city list is not saved yet says so.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA country, city or region name, such as 'Belgium' or 'Antwerp'.
countryCodeNoTwo-letter country code, such as 'be', to look up cities and regions in that country too.

Output Schema

NameRequiredDescriptionDefault
exactYes
placesYes
countriesYes
placesSavedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and openWorldHint=false; the description earns credit by making that concrete ('Free: it reads the saved location lists and never fetches anything') and by disclosing two behaviors annotations cannot express: fuzzy fallback for misspelled names and a clear 'not saved yet' response for un-cached city lists. It stops short of describing result ordering or how many candidates a fuzzy miss returns.

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?

Front-loaded with the core action in the first clause, then the downstream rationale, then the fallback/error behavior, then the cost note — a sensible ordering with no filler sentences. The middle sentence is dense and runs long, which costs a point on readability.

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?

For a 2-parameter read-only resolver with full schema coverage and an output schema, the description covers purpose, downstream consumption, fallback behavior, and the 'not yet saved' edge case. Nothing an agent needs in order to call it 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%, so the baseline is 3; the description adds real meaning on top by explaining why the query should be a country (that is what the downstream locationCode expects) and by tying countryCode to the expansion of results into cities and regions. It does not add format examples beyond what the schema already gives ('Belgium', 'be').

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?

Specific verb and resource: 'looks up the numeric location code a place has.' It also states the downstream purpose (the locationCode that markets keyword, domain, and backlink tools consume) and explicitly frames itself against the failure mode it replaces ('instead of guessing one'), so an agent can tell what it is for without opening the 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?

Clear usage context: use it to resolve a place name to a locationCode before calling the market/domain/backlink tools, and pass countryCode to widen the lookup to cities and regions. There is no explicit 'when not to use' clause, but the caller situation is unambiguous and no plausible alternative tool exists among the siblings.

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.

Resources