Skip to main content
Glama

Get address location

well_get_address_location
Read-only

Find a postal address in the official open address base of its country: France (Base Adresse Nationale) and the United States (Census Bureau geocoder). Use it to check that an address exists, to write it in its official form (street, postal code, town) or to get its point (latitude, longitude). It reads no business, no person and no opening hours: a place to visit goes to well_search_places.

Pass address, the address on one line as the person wrote it, and country (FR, US).

Returns status "found" with up to 3 matches, best first, each with label (the official form), postal_code, city, region, latitude, longitude and score (0 to 1, France only: below 0.5 the match is doubtful, so say so). Or status "refused" with refusal: "not_found", "unavailable", "unsupported_country" or "malformed_input"; pass on message and never show the code or invent an address.

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": {
      "address": "<address>",
      "country": "<country>"
    },
    "name": "well_get_address_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe address on one line.
countryYesThe address's country. Well reads FR, US.
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
sourceNo
statusYes
matchesNo
messageNo
refusalNo
successYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / enum
      Previous value: -[
      -  "fr_recherche_entreprises",
      -  "gb_companies_house",
      -  "us_sec_edgar",
      -  "eu_vies",
      -  "gb_hmrc",
      -  "fr_base_adresse_nationale",
      -  "us_census_geocoder",
      -  "nager_public_holidays",
      -  "fr_prix_des_carburants",
      -  "navitia_journeys"
      -]New value: +[
      +  "fr_recherche_entreprises",
      +  "gb_companies_house",
      +  "us_sec_edgar",
      +  "eu_vies",
      +  "gb_hmrc",
      +  "fr_base_adresse_nationale",
      +  "us_census_geocoder",
      +  "nager_public_holidays",
      +  "fr_prix_des_carburants",
      +  "navitia_journeys",
      +  "youtube_oembed",
      +  "fr_bodacc"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive and open-world, and the description goes further by disclosing the return contract: status found/refused, up to 3 matches best-first, the score threshold of 0.5 and how to describe a doubtful result, plus handling of refusal messages. It still does not mention rate limits, quotas or latency, so a 4 rather than 5.

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 purpose and sibling routing, then parameters, then return shape; no filler sentences. It is dense rather than short, and the returns paragraph partly overlaps with the existing output schema, but every sentence still carries information an agent acts on.

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 read-only lookup tool with five well-described parameters and an output schema, the description covers scope, inputs, return values and the instruction not to invent an address. Nothing an agent needs in order to call it correctly or report results 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, but the description adds real meaning: address must be a single line exactly as the person wrote it, and country is effectively limited to FR and US even though the schema enum lists every ISO code. That narrowing is the key operational detail the schema cannot convey.

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 names a specific verb (find) and resource (a postal address in the official open address base), scopes it to two named sources (Base Adresse Nationale, US Census geocoder), and states the three concrete jobs it serves. It distinguishes itself from well_search_places by explicitly pushing place lookups elsewhere.

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 when-to-use cases (verify existence, produce the official form, obtain coordinates) and a when-not case with the alternative named: a place to visit goes to well_search_places, and it reads no business, person or opening-hours data. Nothing is left to inference about the boundary.

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