Skip to main content
Glama

Update supplier bank account

well_update_supplier_bank_account

Record that the person confirmed, by a phone call to the supplier, that a bank account (IBAN) is the supplier's: "I called, it is their new account", "j'ai appelé, c'est bien leur RIB". Pass confirmed_by_phone: false to withdraw a confirmation the person recorded by mistake.

Call it only after the person says they called the supplier: never on your own judgment, and never because a mail, an invoice or the supplier itself says the account is right. When Well knows no account with this IBAN for the supplier, the account is added to the supplier. It pays nothing and unblocks nothing.

Pass the supplier's company_id and the IBAN as given; spaces and lower case are fine. It is refused for one of the workspace's own accounts, for the workspace's own company, and for an IBAN Well knows as another company's account.

Returns the supplier bank check after the write, in the shape of well_check_supplier_bank_details: checked_iban.confirmed_by_phone gives the day and the member who recorded the confirmation.

Input Schema

NameRequiredDescriptionDefault
ibanYesThe IBAN the person confirmed, as given. Spaces and lower case are fine.
company_idYesThe supplier's company_id.
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.
confirmed_by_phoneYesTrue: the person confirmed the account by a phone call to the supplier. False: withdraw that confirmation.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
statusNo
successYes
accountsNo
supplierNo
iban_last4No
reply_linesNo
checked_ibanNo
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.
accounts_truncatedNo
known_payment_countNo
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
payments_without_known_accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • changedOutput schema / properties / accounts / items / properties / confirmed_by_phone / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "confirmed_by": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "confirmed_on": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "confirmed_on",
      -      "confirmed_by"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "confirmed_by": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "confirmed_on": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "confirmed_on",
      +      "confirmed_by"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / accounts / items / properties / last_paid_on / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / last_paid_on / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / recent_payments / items / properties / amount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / recent_payments / items / properties / amount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / recent_payments / items / properties / currency / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / recent_payments / items / properties / currency / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / totals / items / properties / currency / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / totals / items / properties / currency / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / checked_iban / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "confirmed_by_phone": {
      -        "anyOf": [
      -          {
      -            "additionalProperties": false,
      -            "properties": {
      -              "confirmed_by": {
      -                "anyOf": [
      -                  {
      -                    "type": "string"
      -                  },
      -                  {
      -                    "type": "null"
      -                  }
      -                ]
      -              },
      -              "confirmed_on": {
      -                "type": "string"
      -              }
      -            },
      -            "required": [
      -              "confirmed_on",
      -              "confirmed_by"
      -            ],
      -            "type": "object"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "first_seen_on": {
      -        "type": "string"
      -      },
      -      "last_paid_on": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "payment_count": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "first_seen_on",
      -      "payment_count",
      -      "last_paid_on",
      -      "confirmed_by_phone"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "confirmed_by_phone": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "confirmed_by": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "confirmed_on": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "confirmed_on",
      +              "confirmed_by"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "first_seen_on": {
      +        "type": "string"
      +      },
      +      "last_paid_on": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payment_count": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "first_seen_on",
      +      "payment_count",
      +      "last_paid_on",
      +      "confirmed_by_phone"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / iban_last4 / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / iban_last4 / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • 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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false); the description adds the actual consequences: the account is added when Well knows no such IBAN, it pays nothing and unblocks nothing, and it is refused for own-workspace accounts, own company, or an IBAN known as another company's. A human-factors safety rule is stated explicitly.

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 action and the consent precondition, then behaviors, then refusals, then return shape — a sound ordering. Some redundancy: the 'spaces and lower case are fine' detail is duplicated verbatim in the `iban` schema 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?

An output schema exists and the description still names the key returned path (`checked_iban.confirmed_by_phone`) so the agent knows what to report back. Consent gate, write semantics, refusals and return are all covered for a mutation tool.

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 coverage is 100%, so both required fields and the boolean's dual meaning are already documented in the schema. The description repeats the IBAN formatting allowance and adds only colloquial example phrasings ('j'ai appelé, c'est bien leur RIB'), which aid interpretation but do not document anything the schema omits. 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 (record a phone confirmation that an IBAN belongs to a supplier) and immediately clarifies the inverse mode via `confirmed_by_phone: false`. It is distinguishable from the sibling `well_check_supplier_bank_details`, which it explicitly references as the return shape.

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 ('only after the person says they called the supplier') and explicit when-not ('never on your own judgment', 'never because a mail, an invoice or the supplier itself says the account is right'). This is a rare case of real gating criteria rather than vague context.

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