Ninja MCP

Overview Schema Source Related Servers Discussions Admin

Create Payable Checkout

ninja_create_checkout

Create or recover a pending, unpaid checkout request for retail, pharmacy, beauty, or restaurant verticals. Requires address and line items; does not process payment.

Instructions

Create or recover a pending Ninja checkout/payment request. This creates an unpaid order/payment request; it does not pay.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "confirmCreateOrder": "<confirmCreateOrder>",
      "addressId": "<addressId>",
      "lineItems": "<lineItems>"
    },
    "name": "ninja_create_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`notes`	No
`pharmacy`	No
`vertical`	No		RETAIL
`addressId`	Yes
`lineItems`	Yes
`couponCode`	No
`restaurant`	No
`selectedAwardId`	No
`confirmCreateOrder`	Yes	Set true to run the live createOrder mutation.
`expectedTotalCents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, description carries full burden. It discloses that tool does not pay (key behavioral trait) but omits side effects, idempotency, or recovery specifics. Adequate but not comprehensive.

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, front-loaded with purpose. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (10 params, nested objects, no output schema, no annotations), description is too minimal. Missing return value, error conditions, recovery details, and parameter context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10%. Description does not explain any parameters beyond what the schema already provides. For 10 params including nested objects, more explanation is needed.

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 creates or recovers a pending checkout/payment request and explicitly notes it does not pay. Title 'Create Payable Checkout' further clarifies. Distinguishes from payment and draft order sibling tools.

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?

Impiles use for creating/recovering unpaid checkouts but does not explicitly state when to use vs alternatives like ninja_create_draft_order or payment tools. No when-not or prerequisite conditions provided.

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