Papaya Pay Any Bill (USA)

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

Check Payment Method

check_payment_method

Read-only

Optional: check whether the user has finished the secure form and a card is on the bill yet. Returns the card's last 4 digits and name when one is set, or a PENDING status when the form has not been completed. Use only if you need to confirm the card landed (e.g. the user asks) - it is not a required step; the normal path is analyze_bill -> user fills the form -> confirm_payment_intent.

Args:
    check_input: the user_id and bill_id to look up

Input Schema

TableJSON Schema

Name	Required	Description	Default
`check_input`	Yes	Identifiers to look up whether a card has been set on a bill yet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedJul 13, 2026

removedInput schema / $defs

Removed value: -{
-  "PaymentMethodCheckInput": {
-    "description": "Identifiers to look up whether a card has been set on a bill yet.",
-    "properties": {
-      "bill_id": {
-        "description": "identifier for the bill",
-        "pattern": "^[a-zA-Z0-9]{10}$",
-        "title": "Bill Id",
-        "type": "string"
-      },
-      "user_id": {
-        "description": "identifier for the user the bill belongs to",
-        "pattern": "^[a-zA-Z0-9]{10}$",
-        "title": "User Id",
-        "type": "string"
-      }
-    },
-    "required": [
-      "user_id",
-      "bill_id"
-    ],
-    "title": "PaymentMethodCheckInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / check_input / $ref
```
Removed value: -"#/$defs/PaymentMethodCheckInput"
```

addedInput schema / properties / check_input / description

Added value: +"Identifiers to look up whether a card has been set on a bill yet."

addedInput schema / properties / check_input / properties

Added value: +{
+  "bill_id": {
+    "description": "identifier for the bill",
+    "pattern": "^[a-zA-Z0-9]{10}$",
+    "title": "Bill Id",
+    "type": "string"
+  },
+  "user_id": {
+    "description": "identifier for the user the bill belongs to",
+    "pattern": "^[a-zA-Z0-9]{10}$",
+    "title": "User Id",
+    "type": "string"
+  }
+}

addedInput schema / properties / check_input / required
```
Added value: +[
+  "user_id",
+  "bill_id"
+]
```
addedInput schema / properties / check_input / title
```
Added value: +"PaymentMethodCheckInput"
```
addedInput schema / properties / check_input / type
```
Added value: +"object"
```

First observedJul 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavioral context beyond that: it describes the possible return states (card last4/name or PENDING) and clarifies this is an optional check, not a required step. This is useful context not present in the annotation.

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 concise but complete: every sentence adds value—optionality, return behavior, usage guidance, and argument mapping. It is front-loaded with the purpose and avoids 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?

For a simple read-only lookup tool with an output schema, annotations, and a clear usage note, the description fully covers when and why to use it. It also communicates the normal workflow context without needing to explain return values in detail.

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 provides 100% coverage with descriptions for bill_id and user_id, so the description's phrase 'the user_id and bill_id to look up' adds little beyond what the schema states. Baseline 3 is appropriate.

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 a specific verb and resource: 'check whether the user has finished the secure form and a card is on the bill yet.' It also explicitly distinguishes its role from sibling tools by referencing the normal path (analyze_bill -> user fills form -> confirm_payment_intent), making its niche unmistakable.

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?

Provides explicit when-to-use guidance: 'Use only if you need to confirm the card landed (e.g. the user asks) - it is not a required step.' It also names the normal workflow and thus implicitly tells when not to use it.

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?