Laso Finance

list_payment_recipients

Read-onlyIdempotent

List saved Venmo and PayPal recipients (free)

Lists the Venmo or PayPal recipients this account has paid before, so you can resolve a name your human said ("send $20 to Jane") into the handle that GET /send-payment takes as its recipient_id. Free — only the payout itself is a paid action.

Two different ids are in play. Each entry's recipient_id is an opaque saved-entry id: pass it to POST and DELETE /payment-recipients. Its handle is the phone number or email you actually pay: pass that as recipient_id to GET /send-payment. Passing the saved-entry id to GET /send-payment does not send to the saved person.

Use total_sent and last_sent_timestamp to disambiguate similar names, and confirm with your human rather than guessing between two entries.

Input Schema

Name	Required	Description	Default
`platform`	Yes	Payment platform whose saved recipients to list.
`include_archived`	No	Include archived entries. Defaults to false.

Output Schema

Name	Required	Description
`user_id`	No
`platform`	No	One of: venmo, paypal.
`recipients`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / auth_token

Removed value: -{
-  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "platform": {
+      "description": "One of: venmo, paypal.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "recipients": {
+      "items": {
+        "properties": {
+          "display_name": {
+            "description": "The label the account owner chose. Prefer it when confirming a payment back to a human.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "handle": {
+            "description": "What to pay them at: a 10-digit phone number for Venmo, an email address for PayPal. Pass this as `recipient_id` to `GET /send-payment`.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_sent_timestamp": {
+            "description": "Milliseconds since the epoch.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "The recipient's own name on the platform.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "recipient_id": {
+            "description": "Opaque id of this saved entry (for example `aQ3xK9mZpL2vB7nR4tYw`). Pass it as `recipient_id` to `POST` and `DELETE /payment-recipients`. It is not what `GET /send-payment` takes; use `handle` there.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "send_count": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "total_sent": {
+            "description": "Total dollars sent to this recipient from this account.",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "user_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / platform / description
```
Added value: +"Payment platform whose saved recipients to list."
```

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / platform / description

Removed value: -"Payment platform whose saved recipients to list."

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "platform": {
-      "description": "One of: venmo, paypal.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "recipients": {
-      "items": {
-        "properties": {
-          "display_name": {
-            "description": "The label the account owner chose. Prefer it when confirming a payment back to a human.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "handle": {
-            "description": "What to pay them at: a 10-digit phone number for Venmo, an email address for PayPal. Pass this as `recipient_id` to `GET /send-payment`.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "last_sent_timestamp": {
-            "description": "Milliseconds since the epoch.",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "name": {
-            "description": "The recipient's own name on the platform.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "recipient_id": {
-            "description": "Opaque id of this saved entry (for example `aQ3xK9mZpL2vB7nR4tYw`). Pass it as `recipient_id` to `POST` and `DELETE /payment-recipients`. It is not what `GET /send-payment` takes; use `handle` there.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "send_count": {
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "status": {
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "total_sent": {
-            "description": "Total dollars sent to this recipient from this account.",
-            "type": [
-              "number",
-              "null"
-            ]
-          }
-        },
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "user_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

First observedSep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description exposes a subtle behavioral trap: two different id types exist, and using the wrong one silently fails to send to the intended person. It also explains how total_sent and last_sent_timestamp help disambiguate similar entries, adding genuine value not present in annotations or schema.

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 purpose, then adds high-value operational warnings and disambiguation guidance. Every sentence contributes meaningful information, and the length is justified by the need to prevent a real misuse of recipient identifiers.

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?

Given the output schema exists to describe return values, the description covers everything else needed for a safe and correct call: the supported platforms, the free nature, the identifier distinction, and how to handle ambiguous names. No critical operational context is missing.

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 input schema already documents both parameters with 100% coverage, including enums for platform and a default for include_archived. The description adds context about Venmo/PayPal and the overall purpose, but it does not significantly deepen the meaning of the two input parameters beyond what the schema provides, so the baseline score 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?

The description opens with a precise verb-resource pair: 'List saved Venmo and PayPal recipients', and then clarifies the exact scope ('recipients this account has paid before'). It also clearly distinguishes this tool from related operations like GET /send-payment and recipient management endpoints, so an agent can select it accurately.

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?

The description gives a concrete scenario: resolving a spoken name into a handle before calling GET /send-payment. It explicitly contrasts the free listing action with the paid payout and warns against passing the saved-entry id to GET /send-payment, which is an effective when-not-to behavior.

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

All Laso Finance tools Inspect

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

Need Help?