Skip to main content
Glama

Render a caller-computed cash position

well_render_cash_position
Read-only

Put a cash position YOU computed onto the cash card.

This tool measures nothing. It takes the figure and its method as input and returns them for rendering. Call it only after you have totalled the balances yourself and can state every field below from your own work — never to "get" a cash position.

The server checks the scope against the saved cash scope and refuses a mismatch; computed_by: "caller" covers only the total's arithmetic.

The server derives no cash figure of its own here, so every input in the REQUIRED list must state the policy behind the number and make it checkable.

The result includes unsettled_ownership, the server-derived number of accounts whose owner is unanswered. Do not send it as an input; the server returns it with the figure.

Under the number the card draws nothing. It carries the total and the moment it was read. Every other field below, required or optional, reaches no pixel. All of it comes back in this tool's text result, which is what you write the prose from. The card is the measure; the explanation is yours.

REQUIRED, because a figure whose method is not stated cannot be checked:

  • amount and currency — the consolidated total. NEGATIVE is legal: an overdrawn workspace has negative cash, and this tool renders it rather than refusing it.

  • as_of — the moment the reading is valid for

  • accounts — every account that CONTRIBUTED, each with its native amount and currency, the converted amount, and the rate applied (null when it was already in currency). Carry institution_name and masked_account_number through from the balances read as well: your breakdown names each account by its bank, its name and its masked suffix, or by its currency when the bank and the name are both null, and never by its id.

  • scope: the account types you counted as cash, and whether you counted an account whose ownership tag is unknown but which the workspace marks as owned

  • excluded: the groups that fell out, by reason: not owned, out-of-scope type, no readable balance, or no FX rate. An unanswered owner belongs to no group; the result carries its count as unsettled_ownership. One merged count hides the difference between a rule the reader chose and a defect in the data.

  • partial — whether the total may be a floor (the skills' is_floor), because a balance or FX rate was missing, the own-company set was truncated, or some account's ownership is unsettled. It never means a cut-short read: that stops before this call.

  • own_set_truncated, when true — the balance read reached the own-company row cap. Keep the known ownership verdicts, render their total, and state that it is partial.

REFUSED rather than rendered when one of these checks fails:

  • the caller's scope, accounts or excluded counts differ from the server's check of the saved cash scope. The workspace may have changed since the reads: re-read well_list_cash_scope and well_list_account_balances, then recompute from the latest results instead of changing the arithmetic to fit.

  • a total that is not the sum of the contributions listed — totalling a different set than you disclose publishes a figure nobody can audit

  • a converted amount that does not follow from its native amount and stated rate

  • a rate more than 1% away from Well's stored rate for the pair as of as_of, or a rate for a pair Well stores no rate for (count those accounts in excluded.no_fx_rate). Read rates from exchange_rates; never estimate one.

  • a failure to read the workspace cash scope or balances. A failed stored-rate read is not a refusal: the call fails with a service-side error, and a failed read is never a missing rate.

  • an account already in currency that carries a rate other than one, or whose converted amount differs from its native one

  • an account in another currency that states no rate

  • the same account contributing twice

  • a non-zero total with no contributing accounts

  • an as_of in the future

  • a covers_day that is not the last day of its month — this tool uses it to read a complete month-end balance

  • a covers_day that is not the day as_of falls on

  • a scope.account_types naming nothing

  • a balance_history that repeats a month or runs out of order

  • a currency outside ISO-4217 — checked against the catalog, not its shape

OPTIONAL:

  • covers_day — the UTC day the figure covers, YYYY-MM-DD. A month-end reading covers the last day of that month, and as_of MUST be that day's close, <day>T23:59:59Z. Anything earlier is refused: every rate is checked as of as_of and the stored rate is the latest one on or before it, so a figure covering August stamped earlier in the day converts at the previous day's rate under a caption that says otherwise. A live reading covers no day, so leave the field off — sending it there is an error this tool cannot catch, and it costs the reader the resolution into their own zone that a live reading is meant to get. The card draws a covered day as written, and it cannot tell a covered day from a live moment out of as_of alone: a day's close lands at 23:59:59Z, so every reader east of UTC sees the NEXT day unless you send this.

  • balance_history — trailing complete month ends, oldest first. A null amount is a month no stored row covered; send it as a gap rather than dropping it or sending a zero, and never interpolate between two real points.

OPTIONAL, and send it whenever you computed a cash-flow bridge over the same cash:

  • cash_bridge — { unexplained, closing }, the two terms you sent well_render_cash_flow_bridge, in this card's currency. The server applies the bridge's own tolerance and returns cash_check. "provisional": the bridge does not reconcile, the gap is in unexplained_gap, and the card marks the figure Provisional; say so in prose too: the figure stands on cash with an unexplained gap of that amount. "reconciled": say nothing about it. Leave cash_bridge off when you computed no bridge: the result is cash_check: "not_checked" and the card marks the figure Not checked.

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
as_ofYes
scopeYes
amountYes
partialYes
accountsYes
currencyYes
excludedYes
covers_dayNo
cash_bridgeNoThe cash-flow bridge over the same cash, when you computed one. The server decides whether it reconciles and returns the figure's `cash_check`. Leave it off when you computed no bridge: the figure is then `not_checked`.
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.
balance_historyNo
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.
own_set_truncatedNo

Output Schema

NameRequiredDescriptionDefault
as_ofYes
scopeYes
amountYes
partialYes
successYes
accountsYes
currencyYes
excludedYes
cash_checkNo
covers_dayNo
computed_byYes
balance_historyNo
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.
unexplained_gapNo
own_set_truncatedNo
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
unsettled_ownershipNo
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
    • addedInput schema / properties / scope / properties / counted_unknown_ownership / description
      Added value: +"True only when a counted account has an unknown ownership tag and is marked workspace-owned"
    • addedOutput schema / properties / unsettled_ownership
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed29 schema fields changed
    • removedInput schema / properties / accounts / items / properties / account_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / accounts / items / properties / account_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / accounts / items / properties / fx_rate / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / accounts / items / properties / fx_rate / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / accounts / items / properties / institution_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / accounts / items / properties / institution_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / accounts / items / properties / masked_account_number / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / accounts / items / properties / masked_account_number / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedInput schema / properties / as_of / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • removedInput schema / properties / balance_history / items / properties / amount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / balance_history / items / properties / amount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • addedInput schema / properties / own_set_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / accounts / items / properties / account_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / account_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / fx_rate / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / fx_rate / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / institution_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / institution_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / masked_account_number / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / masked_account_number / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / accounts / items / properties / rate_display / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / accounts / items / properties / rate_display / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / balance_history / items / properties / amount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / balance_history / items / properties / amount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • addedOutput schema / properties / own_set_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • 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"
      +]
    • removedOutput schema / properties / unexplained_gap / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / unexplained_gap / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / accounts / items / properties / rate_display
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The rate as its source publishes it, with no padding zeros: the figure to show."
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools 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. Start the reply with 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."New value: +"Tools 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."
  5. Changed4 schema fields changed
    • addedInput schema / properties / cash_bridge
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The cash-flow bridge over the same cash, when you computed one. The server decides whether it reconciles and returns the figure's `cash_check`. Leave it off when you computed no bridge: the figure is then `not_checked`.",
      +  "properties": {
      +    "closing": {
      +      "description": "The bridge's `closing.amount`, exactly as you sent it to `well_render_cash_flow_bridge`, in this card's currency.",
      +      "type": "number"
      +    },
      +    "unexplained": {
      +      "description": "The bridge's SIGNED `unexplained` gap, exactly as you sent it to `well_render_cash_flow_bridge`, in this card's currency.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "unexplained",
      +    "closing"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / workspace_scope
      Added value: +{
      +  "description": "Restrict 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.",
      +  "enum": [
      +    "family"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / cash_check
      Added value: +{
      +  "enum": [
      +    "reconciled",
      +    "provisional",
      +    "not_checked"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / unexplained_gap
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  6. Changed1 schema field changed
    • addedOutput schema / properties / newly_connected
      Added value: +{
      +  "description": "Tools 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. Start the reply with 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.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "service_id": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "service_id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  7. Changed2 schema fields changed
    • addedInput schema / properties / covers_day
      Added value: +{
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / covers_day
      Added value: +{
      +  "type": "string"
      +}
  8. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id_note
      Added value: +{
      +  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id_source
      Added value: +{
      +  "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
      +  "enum": [
      +    "host_meta",
      +    "argument",
      +    "minted"
      +  ],
      +  "type": "string"
      +}
  9. Changed2 schema fields changed
    • removedOutput schema / properties / caller
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "amount",
      -  "currency",
      -  "as_of",
      -  "accounts",
      -  "scope",
      -  "excluded",
      -  "partial",
      -  "computed_by",
      -  "caller",
      -  "success"
      -]New value: +[
      +  "amount",
      +  "currency",
      +  "as_of",
      +  "accounts",
      +  "scope",
      +  "excluded",
      +  "partial",
      +  "computed_by",
      +  "success"
      +]
  10. 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 readOnlyHint/openWorldHint/destructiveHint annotations: it enumerates every refusal condition (scope mismatch, non-summing total, FX rate >1% off stored rate, duplicate accounts, future as_of, non-month-end covers_day, bad currency), states the 1% rate tolerance, and discloses that a failed stored-rate read is a service error rather than a refusal. It also explains what the card actually draws versus what returns in the text result, plus the server-derived unsettled_ownership and cash_check semantics.

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?

Well front-loaded and organized with headings and bullets, and the emphatic first line earns its place. However, several passages are rhetorically elaborate rather than informational ('The card is the measure; the explanation is yours'; the extended covers_day timezone narration), which lengthens an already dense definition without adding callable detail.

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 14-parameter, nested-object tool with a low-coverage schema, the description supplies everything needed to construct a valid call: required inputs, refusal invariants, workspace routing, and the optional bridge/history semantics. Return-shape detail is appropriately trimmed since an output schema exists, yet the cash_check and unsettled_ownership outcomes are still disclosed.

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 only 29% schema description coverage across 14 parameters, the description carries the burden and does so thoroughly — negative amounts, as_of/covers_day clock coupling, per-account native/converted/rate/null-rate rules, excluded reason breakdown, own_set_truncated, and the cash_bridge terms are all explained. A few nested constraints (e.g. enum limits on account_types, the ISO shape of month) are left to the schema, so it is not exhaustive.

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 ('Put a cash position YOU computed onto the cash card') and immediately delimits the scope with 'This tool measures nothing' — distinguishing it from measurement tools like well_list_account_balances and well_get_computed_figures. An agent can tell exactly what this tool does and does not produce.

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 you have totalled the balances yourself and can state every field below from your own work — never to get a cash position') and names the prerequisite reads (well_list_cash_scope, well_list_account_balances, exchange_rates) plus the sibling it pairs with (well_render_cash_flow_bridge). It also resolves the multi-workspace routing decision directly.

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