Papaya Pay Any Bill (USA)

by com.papayapay.consumer-production.mcp-agent

Analyze Bill

analyze_bill

Read a bill from the user's description and create it for payment. This is the first step. Capture every address and identifier on the bill (remit-to address, account/invoice number, any code or pin) - missing details can delay or fail the payment. The remit-to address (where payment is sent) is especially important: it is what identifies the correct biller, and a wrong or missing one can match the bill to the wrong biller and cause a failed or delayed payment. Always include it. If the bill does not show a remit-to address, research the biller's official remit-to / payment address online and use that rather than omitting it. For the same reason, capture the bill's online-payment URL in payUrl and any payment phone number in otherInfo whenever the bill shows them - these strongly identify the correct biller. Always secure a user identifier so the payment can be applied to the right account or charge: capture the account/customer number in the account field, and any invoice, ticket, or reference number in otherInfo - capture all that the bill shows, since some billers need the account number plus another identifier. If the bill shows none, ask the user for one rather than proceeding without it. Before calling, ask the user how much they want to pay (the full balance amountDue, or a partial amount), then pass it as amount_to_pay and quote what they said in user_amount_statement - both are required (never invent the amount). If the payment carries a fee, the result includes a fees list - show any returned fee to the user before continuing. The result also includes a payment_link: give this link to the user as-is so they can enter their card on the secure form (the only way to set a payment method). If the user already exists from a prior bill, pass their user_id and auth_token to reuse the account.

Args:
    bill_description: structured bill details, including amountDue, amount_to_pay
        and user_amount_statement

Returns:
    bill/user identifiers, tokens, provider, amount due, the chosen amount_to_pay,
    a payment_link to the secure card form, and any user-facing fees

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bill_description`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 5, 2026

removedInput schema / properties / bill_description / properties / remitAddress / anyOf

Removed value: -[
-  {
-    "properties": {
-      "address": {
-        "maxLength": 100,
-        "minLength": 5,
-        "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
-        "title": "Address",
-        "type": "string"
-      },
-      "city": {
-        "maxLength": 50,
-        "minLength": 2,
-        "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
-        "title": "City",
-        "type": "string"
-      },
-      "name": {
-        "maxLength": 50,
-        "minLength": 2,
-        "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
-        "title": "Name",
-        "type": "string"
-      },
-      "stateCode": {
-        "pattern": "^[A-Z]{2}$",
-        "title": "Statecode",
-        "type": "string"
-      },
-      "zip": {
-        "pattern": "^\\d{5}(-\\d{4})?$",
-        "title": "Zip",
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "address",
-      "city",
-      "stateCode",
-      "zip"
-    ],
-    "title": "BillingAddress",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / bill_description / properties / remitAddress / default
```
Removed value: -null
```

changedInput schema / properties / bill_description / properties / remitAddress / description

Previous value: -"Biller remit-to address (where payment is sent). This is the key field for identifying the correct biller - an incorrect or missing remit-to address can cause the bill to be matched to the wrong biller, delaying or failing the payment. Always provide it from the bill. If the bill does not show a remit-to address, research the biller's official remit-to/payment address online and use that rather than leaving it empty."New value: +"Biller remit-to address (where payment is sent). REQUIRED - a bill cannot be analyzed without it. It is the key signal for safely identifying the biller; without a remit-to address (or another strong identifier) the biller may not be identifiable and the bill will be unpayable. Always provide it: take it from the bill, or if the bill does not show one, identify the biller and research their official remit-to / payment address online. Never omit it or invent a placeholder - if you cannot determine a real remit-to address, ask the user for it."

addedInput schema / properties / bill_description / properties / remitAddress / properties

Added value: +{
+  "address": {
+    "maxLength": 100,
+    "minLength": 5,
+    "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
+    "title": "Address",
+    "type": "string"
+  },
+  "city": {
+    "maxLength": 50,
+    "minLength": 2,
+    "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+    "title": "City",
+    "type": "string"
+  },
+  "name": {
+    "maxLength": 50,
+    "minLength": 2,
+    "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+    "title": "Name",
+    "type": "string"
+  },
+  "stateCode": {
+    "pattern": "^[A-Z]{2}$",
+    "title": "Statecode",
+    "type": "string"
+  },
+  "zip": {
+    "pattern": "^\\d{5}(-\\d{4})?$",
+    "title": "Zip",
+    "type": "string"
+  }
+}

addedInput schema / properties / bill_description / properties / remitAddress / required
```
Added value: +[
+  "name",
+  "address",
+  "city",
+  "stateCode",
+  "zip"
+]
```
addedInput schema / properties / bill_description / properties / remitAddress / title
```
Added value: +"BillingAddress"
```
addedInput schema / properties / bill_description / properties / remitAddress / type
```
Added value: +"object"
```

changedInput schema / properties / bill_description / required

Previous value: -[
-  "billerName"
-]New value: +[
+  "remitAddress",
+  "billerName"
+]

Changed3 schema fields changedJul 30, 2026

changedInput schema / properties / bill_description / properties / account / description

Previous value: -"User Account on the bill, if none ticket number"New value: +"The user's account or customer number on the bill (the biller's identifier for the user's account). Capture it whenever the bill shows one. Put any invoice, ticket, or reference number in otherInfo (in addition to the account number - some billers need both), not here."

changedInput schema / properties / bill_description / properties / otherInfo / description

Previous value: -"Other information extracted from the bill that helps identify the provider or complete the payment (like code, pin, pass ...). If the bill shows a payment phone number, include it here (e.g. 'pay_by_phone': '1-800-555-1234') - like the remit-to address it helps identify the correct biller. For a web-payment URL use the payUrl field instead, not this map."New value: +"Other information extracted from the bill that helps identify the provider or complete the payment (like code, pin, pass ...). Also capture the user's charge identifiers here - invoice number, ticket number, or reference number (e.g. 'invoice_number': '12345', 'reference_number': 'A1B2C3') - whenever the bill shows them, even if it also has an account number: some billers' payment automation needs the account number plus one of these. If the bill shows a payment phone number, include it here too (e.g. 'pay_by_phone': '1-800-555-1234') - like the remit-to address it helps identify the correct biller. For a web-payment URL use the payUrl field instead, not this map."

changedInput schema / properties / bill_description / properties / userAddress / description

Previous value: -"User address"New value: +"The payer's identity: the user's name and billing address (who is paying). Billers use this to attribute the payment to the right person, so a missing or wrong payer identity can cause the payment to be rejected or misapplied. Take it from the bill's account-holder / addressee section if shown; otherwise ask the user for their name and billing address rather than leaving it empty."

Changed6 schema fields changedJul 13, 2026

removedInput schema / $defs

Removed value: -{
-  "BillDescription": {
-    "properties": {
-      "account": {
-        "anyOf": [
-          {
-            "pattern": "^(([A-Za-z0-9\\s\\*\\.\\-#]{1,20})|(N/A))$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "User Account on the bill, if none ticket number",
-        "title": "Account"
-      },
-      "amountDue": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Total balance due on the bill (the full amount owed), as read from the bill. This is NOT necessarily what the user will pay - see amount_to_pay.",
-        "title": "Amountdue"
-      },
-      "amount_to_pay": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "The amount the user wants to pay now. May be a partial payment, distinct from amountDue (the bill total). Ask the user how much they want to pay before calling; set equal to amountDue to pay in full. Passing it previews any fee for that amount in the result.",
-        "title": "Amount To Pay"
-      },
-      "auth_token": {
-        "anyOf": [
-          {
-            "pattern": "^[a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "authorization token attached to the user (if a user already exists from a previous bill payment). MUST be the most recent/current auth_token (check latest call with the same user id, possibly in a previous session). Depending how long ago the previous payment was made, may first need to obtain a new token.",
-        "title": "Auth Token"
-      },
-      "billerName": {
-        "description": "Name of the biller",
-        "maxLength": 50,
-        "minLength": 2,
-        "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
-        "title": "Billername",
-        "type": "string"
-      },
-      "correspondenceAddress": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/BillingAddress"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Biller correspondence address"
-      },
-      "dueDate": {
-        "anyOf": [
-          {
-            "pattern": "\\d{1,2}\\s?(/|-)\\s?\\d{1,2}\\s?(/|-)\\s?(\\d{4}|\\d{2})",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Due date for the bill in MM/DD/YYYY format MM/DD/YY is acceptable",
-        "title": "Duedate"
-      },
-      "otherInfo": {
-        "default": {},
-        "description": "Other information extracted from the bill that helps identify the provider or complete the payment (like code, pin, pass ...). If the bill shows a payment phone number, include it here (e.g. 'pay_by_phone': '1-800-555-1234') - like the remit-to address it helps identify the correct biller. For a web-payment URL use the payUrl field instead, not this map.",
-        "patternProperties": {
-          "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$": {
-            "anyOf": [
-              {
-                "type": "number"
-              },
-              {
-                "type": "integer"
-              },
-              {
-                "maxLength": 75,
-                "minLength": 2,
-                "pattern": "^[a-zA-Z0-9 \\-\\./,'&@*#:?=+()]+$",
-                "type": "string"
-              }
-            ]
-          }
-        },
-        "propertyNames": {
-          "maxLength": 50,
-          "minLength": 2
-        },
-        "title": "Otherinfo",
-        "type": "object"
-      },
-      "payUrl": {
-        "anyOf": [
-          {
-            "maxLength": 120,
-            "minLength": 4,
-            "pattern": "^[a-zA-Z0-9\\-._~:/?#\\[\\]@!$&'()*+,;=%]+$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "The web address where the bill can be paid online (the 'pay at' / 'pay online' URL printed on the bill), e.g. https://www.biller.com/pay. Like the remit-to address it strongly identifies the correct biller, so include it whenever the bill shows one to reduce the risk of a misidentified, failed, or delayed payment. Must be a single URL of at most 120 characters (just the base 'pay online' address, no extra text); omit it rather than sending anything longer.",
-        "title": "Payurl"
-      },
-      "remitAddress": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/BillingAddress"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Biller remit-to address (where payment is sent). This is the key field for identifying the correct biller - an incorrect or missing remit-to address can cause the bill to be matched to the wrong biller, delaying or failing the payment. Always provide it from the bill. If the bill does not show a remit-to address, research the biller's official remit-to/payment address online and use that rather than leaving it empty."
-      },
-      "userAddress": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/BillingAddress"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "User address"
-      },
-      "user_amount_statement": {
-        "anyOf": [
-          {
-            "maxLength": 200,
-            "minLength": 3,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Required proof that you asked the user how much to pay and they answered: quote what the user actually said (e.g. 'pay the full 150' or 'just 50 this month'). You MUST have asked the user before setting amount_to_pay - never invent the amount or this quote.",
-        "title": "User Amount Statement"
-      },
-      "user_id": {
-        "anyOf": [
-          {
-            "pattern": "^[a-zA-Z0-9]{10}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "identifier for the user if a user already exists from a previous bill payment",
-        "title": "User Id"
-      }
-    },
-    "required": [
-      "billerName"
-    ],
-    "title": "BillDescription",
-    "type": "object"
-  },
-  "BillingAddress": {
-    "properties": {
-      "address": {
-        "maxLength": 100,
-        "minLength": 5,
-        "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
-        "title": "Address",
-        "type": "string"
-      },
-      "city": {
-        "maxLength": 50,
-        "minLength": 2,
-        "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
-        "title": "City",
-        "type": "string"
-      },
-      "name": {
-        "maxLength": 50,
-        "minLength": 2,
-        "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
-        "title": "Name",
-        "type": "string"
-      },
-      "stateCode": {
-        "pattern": "^[A-Z]{2}$",
-        "title": "Statecode",
-        "type": "string"
-      },
-      "zip": {
-        "pattern": "^\\d{5}(-\\d{4})?$",
-        "title": "Zip",
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "address",
-      "city",
-      "stateCode",
-      "zip"
-    ],
-    "title": "BillingAddress",
-    "type": "object"
-  }
-}

removedInput schema / properties / bill_description / $ref
```
Removed value: -"#/$defs/BillDescription"
```

addedInput schema / properties / bill_description / properties

Added value: +{
+  "account": {
+    "anyOf": [
+      {
+        "pattern": "^(([A-Za-z0-9\\s\\*\\.\\-#]{1,20})|(N/A))$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "User Account on the bill, if none ticket number",
+    "title": "Account"
+  },
+  "amountDue": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Total balance due on the bill (the full amount owed), as read from the bill. This is NOT necessarily what the user will pay - see amount_to_pay.",
+    "title": "Amountdue"
+  },
+  "amount_to_pay": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "The amount the user wants to pay now. May be a partial payment, distinct from amountDue (the bill total). Ask the user how much they want to pay before calling; set equal to amountDue to pay in full. Passing it previews any fee for that amount in the result.",
+    "title": "Amount To Pay"
+  },
+  "auth_token": {
+    "anyOf": [
+      {
+        "pattern": "^[a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "authorization token attached to the user (if a user already exists from a previous bill payment). MUST be the most recent/current auth_token (check latest call with the same user id, possibly in a previous session). Depending how long ago the previous payment was made, may first need to obtain a new token.",
+    "title": "Auth Token"
+  },
+  "billerName": {
+    "description": "Name of the biller",
+    "maxLength": 50,
+    "minLength": 2,
+    "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+    "title": "Billername",
+    "type": "string"
+  },
+  "correspondenceAddress": {
+    "anyOf": [
+      {
+        "properties": {
+          "address": {
+            "maxLength": 100,
+            "minLength": 5,
+            "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
+            "title": "Address",
+            "type": "string"
+          },
+          "city": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "City",
+            "type": "string"
+          },
+          "name": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "Name",
+            "type": "string"
+          },
+          "stateCode": {
+            "pattern": "^[A-Z]{2}$",
+            "title": "Statecode",
+            "type": "string"
+          },
+          "zip": {
+            "pattern": "^\\d{5}(-\\d{4})?$",
+            "title": "Zip",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "address",
+          "city",
+          "stateCode",
+          "zip"
+        ],
+        "title": "BillingAddress",
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Biller correspondence address"
+  },
+  "dueDate": {
+    "anyOf": [
+      {
+        "pattern": "\\d{1,2}\\s?(/|-)\\s?\\d{1,2}\\s?(/|-)\\s?(\\d{4}|\\d{2})",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Due date for the bill in MM/DD/YYYY format MM/DD/YY is acceptable",
+    "title": "Duedate"
+  },
+  "otherInfo": {
+    "default": {},
+    "description": "Other information extracted from the bill that helps identify the provider or complete the payment (like code, pin, pass ...). If the bill shows a payment phone number, include it here (e.g. 'pay_by_phone': '1-800-555-1234') - like the remit-to address it helps identify the correct biller. For a web-payment URL use the payUrl field instead, not this map.",
+    "patternProperties": {
+      "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "integer"
+          },
+          {
+            "maxLength": 75,
+            "minLength": 2,
+            "pattern": "^[a-zA-Z0-9 \\-\\./,'&@*#:?=+()]+$",
+            "type": "string"
+          }
+        ]
+      }
+    },
+    "propertyNames": {
+      "maxLength": 50,
+      "minLength": 2
+    },
+    "title": "Otherinfo",
+    "type": "object"
+  },
+  "payUrl": {
+    "anyOf": [
+      {
+        "maxLength": 120,
+        "minLength": 4,
+        "pattern": "^[a-zA-Z0-9\\-._~:/?#\\[\\]@!$&'()*+,;=%]+$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "The web address where the bill can be paid online (the 'pay at' / 'pay online' URL printed on the bill), e.g. https://www.biller.com/pay. Like the remit-to address it strongly identifies the correct biller, so include it whenever the bill shows one to reduce the risk of a misidentified, failed, or delayed payment. Must be a single URL of at most 120 characters (just the base 'pay online' address, no extra text); omit it rather than sending anything longer.",
+    "title": "Payurl"
+  },
+  "remitAddress": {
+    "anyOf": [
+      {
+        "properties": {
+          "address": {
+            "maxLength": 100,
+            "minLength": 5,
+            "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
+            "title": "Address",
+            "type": "string"
+          },
+          "city": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "City",
+            "type": "string"
+          },
+          "name": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "Name",
+            "type": "string"
+          },
+          "stateCode": {
+            "pattern": "^[A-Z]{2}$",
+            "title": "Statecode",
+            "type": "string"
+          },
+          "zip": {
+            "pattern": "^\\d{5}(-\\d{4})?$",
+            "title": "Zip",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "address",
+          "city",
+          "stateCode",
+          "zip"
+        ],
+        "title": "BillingAddress",
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Biller remit-to address (where payment is sent). This is the key field for identifying the correct biller - an incorrect or missing remit-to address can cause the bill to be matched to the wrong biller, delaying or failing the payment. Always provide it from the bill. If the bill does not show a remit-to address, research the biller's official remit-to/payment address online and use that rather than leaving it empty."
+  },
+  "userAddress": {
+    "anyOf": [
+      {
+        "properties": {
+          "address": {
+            "maxLength": 100,
+            "minLength": 5,
+            "pattern": "^[a-zA-Z0-9\\s\\-\\.',#]+$",
+            "title": "Address",
+            "type": "string"
+          },
+          "city": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "City",
+            "type": "string"
+          },
+          "name": {
+            "maxLength": 50,
+            "minLength": 2,
+            "pattern": "^(([a-zA-Z0-9 \\-\\_.,'&]+)|(N/A))$",
+            "title": "Name",
+            "type": "string"
+          },
+          "stateCode": {
+            "pattern": "^[A-Z]{2}$",
+            "title": "Statecode",
+            "type": "string"
+          },
+          "zip": {
+            "pattern": "^\\d{5}(-\\d{4})?$",
+            "title": "Zip",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "address",
+          "city",
+          "stateCode",
+          "zip"
+        ],
+        "title": "BillingAddress",
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "User address"
+  },
+  "user_amount_statement": {
+    "anyOf": [
+      {
+        "maxLength": 200,
+        "minLength": 3,
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Required proof that you asked the user how much to pay and they answered: quote what the user actually said (e.g. 'pay the full 150' or 'just 50 this month'). You MUST have asked the user before setting amount_to_pay - never invent the amount or this quote.",
+    "title": "User Amount Statement"
+  },
+  "user_id": {
+    "anyOf": [
+      {
+        "pattern": "^[a-zA-Z0-9]{10}$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "identifier for the user if a user already exists from a previous bill payment",
+    "title": "User Id"
+  }
+}

addedInput schema / properties / bill_description / required
```
Added value: +[
+  "billerName"
+]
```
addedInput schema / properties / bill_description / title
```
Added value: +"BillDescription"
```
addedInput schema / properties / bill_description / type
```
Added value: +"object"
```

First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description discloses that it creates a bill for payment, that fees may be returned and should be shown, and that a payment_link is returned for card entry. It adds guidance on reusing auth_token for existing users. Annotations already indicate non-read-only, so the description supplements with actionable behavioral details.

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

Conciseness3/5

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

The description is quite long and somewhat repetitive, especially around the remit-to address being critical. It is dense with useful instructions but lacks clear sectioning or bullet points, making it harder for an agent to quickly parse the key directives.

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 description covers all necessary context: required fields, handling missing information, pre-call user questions, reuse of auth tokens, and expected return values (fees, payment_link). Since an output schema exists, the description appropriately supplements rather than duplicates, making it complete for the tool's complexity.

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?

Although the schema includes detailed descriptions for all nested parameters, the tool description adds crucial workflow context: it explains the importance of remitAddress, how to fill amount_to_pay and user_amount_statement, and where to place invoice numbers in otherInfo. This goes beyond the schema's field-level descriptions.

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's function: "Read a bill from the user's description and create it for payment." It also positions it as "the first step" in the payment workflow, distinguishing it from sibling tools like confirm_payment_intent or check_payment_method.

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 provides clear usage context: it is the first step, and it mandates pre-call actions like asking the user for the payment amount and capturing identifiers. It does not explicitly name when NOT to use it or mention alternative tools, but the context is unambiguous.

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

All Papaya Pay Any Bill (USA) 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?