Skip to main content
Glama

Update location

well_update_location
Destructive

Set the address of a company in the current workspace, in one write: the new address replaces one address the company already has, or becomes its first one.

Use this tool when the user asks to change, fix, move, replace or set the address of a company. Do not add the new address with well_add_contact_channel and remove the old one: this tool does both. When the company has no address yet, this tool still applies: omit location_id and the address becomes the company's primary address. Use well_add_contact_channel only when the user wants one more address beside the ones the company keeps.

Read the company's addresses first with well_query_records (company_locations). When the user does not say which address, replace the primary one. When the company has several addresses and none is primary, ask which one, once.

On an invoice draft, pass draft_party with the draft's invoice_id: "receiver" when the company is the draft's customer, "issuer" when it is the company that issues the draft. While the conversation has an open draft, a call on the workspace's own company without draft_party is refused before any confirmation: an address the person gives on a draft is the customer's unless they say it is their own company's, and when their words do not say which, ask them in one line first. A customer who is a private individual has no company: write their address with well_add_contact_channel (parent person).

REQUIRED: parent ("company"), parent_id (the company id), address (the new address: at least one of address_line1, postal_code or city). OPTIONAL: location_id (the id of the address to replace; omit it only when the company has no address), draft_party ({ invoice_id, party }). In address: address_line2, region, subdivision_code (ISO 3166-2, such as FR-IDF), country (2-letter ISO code). Pass the whole new address, not only the part that changes.

The old address is kept as a removed row; the new one takes its place, with the same label and the same primary flag. A call without location_id on a company that has an address, or with a location_id that is not a live address of the company, is refused before any confirmation.

Returns { success: true, location_id, address } on success, where location_id is the id of the new address and address is the new address on one line, or { success: false, error } on failure.

Input Schema

NameRequiredDescriptionDefault
parentYesThe record the address belongs to: company
addressYesThe new address, whole
parent_idYesUUID of the company
draft_partyNoSet on an invoice draft: the call is refused unless the company is this party of the draft
location_idNoUUID of the address to replace, read with well_query_records; omit when the company has no address
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
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.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
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
codeNo
errorNo
addressNo
successYes
location_idNo
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
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.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / near_candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "company_id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "company_id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / near_candidates_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / address / properties / subdivision_code
      Added value: +{
      +  "description": "ISO 3166-2 code such as FR-IDF; kept only when its prefix is the address country",
      +  "maxLength": 6,
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / draft_party
      Added value: +{
      +  "description": "Set on an invoice draft: the call is refused unless the company is this party of the draft",
      +  "properties": {
      +    "invoice_id": {
      +      "description": "UUID of the invoice draft being worked on",
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    },
      +    "party": {
      +      "description": "receiver = the draft's customer; issuer = the company that issues it",
      +      "enum": [
      +        "receiver",
      +        "issuer"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "invoice_id",
      +    "party"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true): it discloses that the old address is retained as a removed row, that the new row inherits the label and primary flag, and the exact refusal conditions (missing location_id when an address exists, a location_id that is not a live address, and a call on the workspace's own company without draft_party while a draft is open). It also explains the draft party rules and the private-individual escape hatch.

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, then usage, then the draft-specific rule, then parameters and returns — a sound structure. It is long, and the REQUIRED/OPTIONAL block largely restates the schema, which is the main redundancy in an otherwise efficient description.

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 9-parameter destructive mutation with nested objects, it covers selection, prerequisites, refusal conditions, draft edge cases, the soft-delete effect, and both success and failure return shapes. Nothing an agent needs 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?

With 100% schema coverage the baseline is 3, and the description does add real meaning: 'pass the whole new address, not only the part that changes', the rule that location_id is omitted only when no address exists, and the semantics of draft_party against a draft. Much of the REQUIRED/OPTIONAL recap repeats the schema descriptions, which keeps this just short of a 5.

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 opening sentence names a precise verb and resource (set the address of a company in the current workspace) and specifies the two outcomes: replaces an existing address or becomes the first one. It explicitly distinguishes itself from well_add_contact_channel, so the agent can choose without opening 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 Guidelines5/5

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

Gives explicit when-to-use triggers ('change, fix, move, replace or set'), explicit when-not ('do not add the new address with well_add_contact_channel and remove the old one'), the alternative for adding an address, a prerequisite read step (well_query_records company_locations), and a disambiguation rule for multiple addresses. Nothing about tool selection is left to inference.

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