Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

delete_payment_recipient

DestructiveIdempotent

Remove a saved recipient (free)

Removes a saved Venmo or PayPal recipient. Payment history is kept; only the saved entry stops being offered.

This is not reversible through the API, so prefer archiving (POST /payment-recipients with archived: true) when the account owner may want the recipient back, and confirm before removing someone they did not ask you to remove.

platform and recipient_id may be sent in the JSON body or the query string.

Input Schema

NameRequiredDescriptionDefault
platformNoRequired unless sent in the body.
recipient_idNoRequired unless sent in the body. The entry's `recipient_id` from `GET /payment-recipients` (an opaque id, not the phone number or email).

Output Schema

NameRequiredDescriptionDefault
deletedNo
user_idNo
recipient_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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": {
+    "deleted": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "recipient_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "user_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "deleted": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "recipient_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "user_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds meaningful behavior: the action is not reversible through the API, payment history is kept, only the saved entry stops being offered, and parameters may go in body or query string. No contradiction with annotations.

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?

The description is well organized and efficient: it states the action, the irreversible consequence, the preferred alternative, and the transport option. Slight redundancy between the opening title and first sentence, but every sentence earns its place.

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 two-parameter deletion tool with an output schema, the description covers all essential operational facts: irreversibility, history preservation, alternative archiving behavior, consent caution, and body/query flexibility. Nothing critical is missing.

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 adds genuinely useful transport semantics by stating that `platform` and `recipient_id` may be sent in the JSON body or query string, and clarifies that `recipient_id` is the opaque id from `GET /payment-recipients`, not the phone number or email.

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 uses a specific verb and resource: 'Removes a saved Venmo or PayPal recipient.' It clearly distinguishes this from sibling tools like delete_banking_recipient by naming the payment recipient scope and noting that payment history is preserved.

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 explicitly tells the agent when to prefer an alternative: archive via `POST /payment-recipients` with `archived: true` when the owner may want the recipient back. It also instructs to confirm before removing someone the owner did not ask to remove, providing clear selection 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