Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_payment_status

Check Venmo and PayPal payout status (free)

Reports the state of the Venmo and PayPal payouts this account has sent with GET /send-payment. Free: only the payout itself is a paid action.

Three ways to call it: with payment_id to fetch one payout, with recipient_id (from GET /payment-recipients) to list every payout to that saved recipient, or with neither to list every payout this account has sent, newest first.

state is queued (waiting on account balance), in-process (dispatched to the platform), complete, failed, or cancelled. queued and in-process are the two states still in flight; poll every few minutes, or register a webhook with POST /register-webhook to be told when a payout completes instead. A payout that has been in-process for more than an hour is worth raising with the account owner. state is absent on payouts sent before state tracking existed.

Bank payouts are not listed here: follow those with listBankingTransactions. Push-to-card transfers are completed by the recipient in the browser and have no server-side state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.
payment_idNoFetch one payout by its `id`. Takes precedence over `recipient_id`.
recipient_idNoList every payout to one saved recipient. This is the `recipient_id` returned by `GET /payment-recipients`, not the phone number or email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "payment": {
-          "description": "One Venmo or PayPal payout sent from this account.",
-          "properties": {
-            "amount_pre_fees": {
-              "description": "Dollars the recipient receives.",
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "amount_with_fees": {
-              "description": "Dollars debited from the account balance, fee included.",
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "fees_paid": {
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "id": {
-              "description": "Pass as `payment_id` to fetch this payout on its own.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "platform": {
-              "description": "One of: venmo, paypal.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "recipient_first_name": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "recipient_id": {
-              "description": "The saved recipient this went to, as returned by `GET /payment-recipients`.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "recipient_last_name": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "state": {
-              "description": "`queued` and `in-process` are still in flight. Absent on payouts sent before state tracking existed. One of: queued, in-process, complete, failed, cancelled.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "state_updated_at": {
-              "description": "Milliseconds since the epoch when `state` last changed.",
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "timestamp": {
-              "description": "Milliseconds since the epoch when the payout was sent.",
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "timestamp_readable": {
-              "type": [
-                "string",
-                "null"
-              ]
-            }
-          },
-          "type": [
-            "object",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    {
-      "properties": {
-        "payments": {
-          "items": {
-            "description": "One Venmo or PayPal payout sent from this account.",
-            "properties": {
-              "amount_pre_fees": {
-                "description": "Dollars the recipient receives.",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "amount_with_fees": {
-                "description": "Dollars debited from the account balance, fee included.",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "fees_paid": {
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "id": {
-                "description": "Pass as `payment_id` to fetch this payout on its own.",
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "platform": {
-                "description": "One of: venmo, paypal.",
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "recipient_first_name": {
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "recipient_id": {
-                "description": "The saved recipient this went to, as returned by `GET /payment-recipients`.",
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "recipient_last_name": {
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "state": {
-                "description": "`queued` and `in-process` are still in flight. Absent on payouts sent before state tracking existed. One of: queued, in-process, complete, failed, cancelled.",
-                "type": [
-                  "string",
-                  "null"
-                ]
-              },
-              "state_updated_at": {
-                "description": "Milliseconds since the epoch when `state` last changed.",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "timestamp": {
-                "description": "Milliseconds since the epoch when the payout was sent.",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "timestamp_readable": {
-                "type": [
-                  "string",
-                  "null"
-                ]
-              }
-            },
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses the free nature, enumerates all possible state values and their meanings, notes that state is absent for older payouts, and clarifies that push-to-card transfers have no server-side state. It also flags that in-process over an hour warrants investigation. This is comprehensive behavioral disclosure.

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?

While the description is longer than average, every sentence earns its place: it covers call modes, state meanings, polling guidance, webhook alternative, and exclusions. It is well-structured and front-loads the core purpose, then provides necessary detail without fluff.

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?

The tool has three distinct call patterns and a complex state model. The description fully explains when to use each pattern, what the state field means, and how to handle in-flight states. It also clarifies what is not covered (bank payouts, push-to-card), leaving no gaps for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides 100% coverage with descriptions for all three parameters. The description adds critical semantics: payment_id takes precedence over recipient_id, and recipient_id must be the ID returned by GET /payment-recipients, not phone/email. It also explains the 'neither' case, which is not in the schema. This adds substantial meaning beyond the schema.

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 clearly states the tool checks Venmo and PayPal payout status, naming the specific action and resource. It differentiates from siblings by explicitly noting that bank payouts are not listed here and should be followed via listBankingTransactions, and it distinguishes from push-to-card transfers.

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?

It gives three explicit invocation patterns (with payment_id, with recipient_id, or with neither) and explains what each returns. It also advises when to poll versus register a webhook, and directs users to the appropriate alternative for bank payouts. This is thorough, actionable usage guidance.

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