Ninja MCP

Overview Schema Source Related Servers Discussions Admin

Saved Payment Options

ninja_saved_payment_options

List saved payment options, cards, and wallets for an account. Optionally specify an amount to check availability via pending checkout methods.

Instructions

List account-level payment options, saved cards, and wallets for an optional amount. Use pending checkout methods for actual checkout availability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ninja_saved_payment_options"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	No	Optional amount in SAR units.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided; description implies read-only operation via 'list' verb. It does not disclose potential limitations or side effects, but the context is sufficient for a list operation.

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?

Two concise sentences, directly stating purpose and usage guidance. No unnecessary words.

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?

Given one optional parameter and no output schema, the description fully covers what the tool does and when to use it, with no missing context.

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% with a single parameter 'amount' described in the schema. The description adds 'for an optional amount' which mirrors the schema, not adding significant new meaning.

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?

Description clearly states it lists account-level payment options, saved cards, and wallets for an optional amount. This distinguishes it from sibling tools like ninja_pending_payment_methods which are for actual checkout availability.

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?

Explicitly guides to use pending checkout methods for actual checkout availability, providing clear when-to and when-not-to context.

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