Darwin

List payment methods

list_payment_methods

Read-onlyIdempotent

List a cursor page of saved payment method references for the authorized account with status, rail and default selection. Continue with nextCursor as afterCursor until null. Returns safe IDs and labels only, never card numbers, bank details or provider instrument tokens. A saved method is not approval to spend.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum saved methods to return, up to 100.
`afterCursor`	No	Continue after the previous response nextCursor.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`methods`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

removedInput schema / properties / actingAiId

Removed value: -{
-  "description": "Authorized Darwin AI whose saved payment method references to list.",
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "actingAiId"
-]
```

Changed4 schema fields changedSep 29, 2026

addedInput schema / properties / afterCursor

Added value: +{
+  "description": "Continue after the previous response nextCursor.",
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum saved methods to return, up to 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / nextCursor

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9_-]+$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "methods"
-]New value: +[
+  "methods",
+  "nextCursor"
+]

AddedSep 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-structured context: only safe IDs and labels are returned, never card numbers, bank details or provider instrument tokens, plus the caveat that a saved method is not spend approval. That is useful safety framing beyond the annotation set, though it omits error/rate behavior.

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?

Four tight sentences, front-loaded with what is listed and scoped, followed by pagination mechanics and the data-safety caveat. No filler or repetition.

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?

An output schema exists, so return structure need not be described, and the description still covers pagination termination, field scope and data-exposure limits. Combined with the annotations, nothing an agent needs to call this correctly 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?

Schema coverage is 100% and both parameters are fully documented there, so the baseline is 3. The description adds only the termination condition ('until null') on top of the schema's explanation of afterCursor, no new syntax or format detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (saved payment method references) with the account scope and the fields returned (status, rail, default selection). 'Saved payment method references' is distinguishable from the credential-oriented sibling list_auth_credentials, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives pagination usage clearly ('Continue with nextCursor as afterCursor until null'), which is real guidance for invoking it repeatedly. It does not say when to prefer this over list_auth_credentials or get_account, so the when-to-use dimension is only implied.

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

All Darwin tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?