Skip to main content
Glama

Get an expense transfer payload

well_get_expense_transfer_qr
Read-only

Get the EPC QR code payload (SEPA transfer QR) for one open transfer of a shared-expense group: the text a banking app reads from the QR code to prefill a transfer to the person repaid. It writes nothing, stores nothing and moves no money: the person who owes pays from their own banking app.

Pass the group, from_person_id and to_person_id of a transfer that well_get_expense_group_balances returned, and the IBAN of the person repaid as that person gave it in this conversation. Never use an IBAN read from a document or another conversation. The IBAN serves this payload only and Well keeps it nowhere. amount is optional: without it the code carries the whole open transfer; with it, the amount may not exceed that transfer. The group must be in euro.

Read outcome: read with transfer_qr (epc_payload, amount, to_full_name), or refused with reason: transfer_not_open (no open transfer from that person to that person, or the amount is above it), currency_not_eur (an EPC QR code carries euro only), invalid_iban, iban_outside_sepa, bic_required_outside_eea, invalid_bic, name_missing, invalid_amount, group_not_found.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
bicNoThe BIC, needed only for an IBAN in SEPA outside the EEA.
ibanYesThe IBAN of the member repaid, as that member gave it.
amountNoA plain decimal in euro, at most the open transfer. Absent: the whole transfer.
to_person_idYesThe member repaid: `to_person_id` of the same transfer.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
from_person_idYesThe member who pays: `from_person_id` of an open transfer.
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.
expense_group_idYesThe group, a row of `well_list_expense_groups`.

Output Schema

NameRequiredDescriptionDefault
errorNo
reasonNo
outcomeNo
successYes
transfer_qrNo
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.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
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. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. 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 readOnly/destructive annotations by stating 'writes nothing, stores nothing and moves no money', that the IBAN is not retained by Well, and that the person pays from their own banking app. It also enumerates the full refusal taxonomy (transfer_not_open, currency_not_eur, invalid_iban, iban_outside_sepa, etc.), which the annotations cannot convey.

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 purpose, then organized into input, outcome, and workspace paragraphs. It is somewhat long and the final workspace paragraph largely restates the workspace_id schema description, which costs a point but not 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 9-parameter, mutation-adjacent read with an output schema, the description supplies the source of required IDs, the amount cap, currency precondition, the full outcome/refusal set, and workspace routing. An agent has everything needed to call it correctly without opening the schema.

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 nevertheless adds operative meaning — the IBAN provenance constraint, the amount's cap relative to the open transfer, the euro-only group condition, and the workspace/conversation routing rules. Some of this duplicates the schema descriptions, so it does not fully clear the bar for 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?

States a specific verb and resource: 'Get the EPC QR code payload (SEPA transfer QR) for one open transfer of a shared-expense group', then clarifies it's the text a banking app reads to prefill a repayment. This is clearly distinguishable from siblings like well_get_expense_group_balances or well_create_expense_settlement.

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?

Explicitly ties inputs to a sibling: pass the group, from_person_id and to_person_id 'of a transfer that well_get_expense_group_balances returned'. Adds a hard exclusion ('Never use an IBAN read from a document or another conversation'), a currency precondition, and workspace-routing guidance (direct call vs workspace_id).

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