Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

list_bank_recipients

List bank payout recipients (free)

Lists the recipients registered on your banking profile and the destinations attached to each, so you can find the destination_id that GET /send-bank-payment pays out to. Free — only the payout itself is a paid action.

Bank account numbers are returned masked to their last four digits; routing numbers are returned in full. Create recipients and destinations with the createBankingRecipient and addBankingDestination callables, rename a destination's nickname (the only editable field) with updateBankingDestination, and remove a recipient with deleteBankingRecipient (see the bank accounts guide).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "recipients": {
-      "items": {
-        "properties": {
-          "address": {
-            "description": "The payee's postal address, when one is set.",
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "destinations": {
-            "items": {
-              "properties": {
-                "account_holder_name": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "account_number_last4": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "bank_name": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "crypto_address": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "destination_id": {
-                  "description": "Pass this as `destination_id` to `GET /send-bank-payment`.",
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "destination_type": {
-                  "description": "One of: fiat_us, fiat_iban, crypto.",
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "name": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "network_id": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "nickname": {
-                  "description": "User-chosen label, present when one is set. The only editable field on a destination: set it at creation with `addBankingDestination` or later with `updateBankingDestination`.",
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                },
-                "routing_number": {
-                  "type": [
-                    "string",
-                    "null"
-                  ]
-                }
-              },
-              "type": [
-                "object",
-                "null"
-              ]
-            },
-            "type": [
-              "array",
-              "null"
-            ]
-          },
-          "name": {
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "recipient_id": {
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "status": {
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "user_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains the read-only nature, that listing is free while payouts are paid, and reveals sensitive data handling: account numbers masked to last four digits, routing numbers returned in full. It omits pagination or error behavior, but for this simple list operation the disclosure is solid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core sentence, and each subsequent paragraph earns its place: workflow purpose, pricing, output masking, and related operations. There is no fluff or redundant restating.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description conveys what the response contains: recipients, attached destinations, masked account numbers, and full routing numbers. It also links to relevant sibling operations and a guide. Exact response shape is not specified, but enough context is present for correct invocation.

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?

The single optional parameter auth_token is already fully documented in the input schema, so schema description coverage is 100%. The tool description adds no additional parameter semantics, which matches the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: it lists bank payout recipients and the destinations attached to each. However, it does not explicitly differentiate itself from the similarly named sibling list_banking_recipients, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives concrete usage context: use this tool to find the destination_id that send-bank-payment pays out to. It also frames related create/update/delete tools as complementary steps. It does not explicitly state when not to use it, but the workflow guidance is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Laso Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources