Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

createPayment

createPayment

Record a successful manual or offline payment or tax-withheld amount. Link the payment to invoices to reduce the amount due and mark invoices as paid.

Instructions

Record a successful manual/offline payment or tax-withheld amount, equivalent to the frontend Add Payment flow. Link to invoices via payment_parts array. Use type='payment' with payment_method='bank_transfer', 'check', 'cash', or 'card'. Use type='tax_withheld' without payment_method. Always use status='success'. Do not use status='created' for manually recorded payments; created payments are unrealized and will not reduce invoice amount_due or mark invoices paid. The backend assigns the payment timestamp when the payment is recorded. Refunds, authorizations, reversals, payment links, and gateway charge attempts are outside this tool's scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoUUID of the customer making the payment.
amountYesTotal payment amount in the smallest currency unit (e.g. cents).
currency_codeYesThree-letter ISO 4217 currency code (e.g. USD).
payment_partsNoArray of invoice allocations. Each element: {invoice_id: 'UUID', amount: 10000}. Links the payment to one or more invoices.
payment_methodNoManual payment method. Required when type='payment'; omit for type='tax_withheld'. Supported values match the frontend Add Payment flow.
typeNoFrontend Add Payment type. Use 'payment' for a manual/offline payment, or 'tax_withheld' for a tax withheld amount. Refunds, payment reversals, and authorizations are outside this tool's scope.payment
statusNoPayment status for this recorded payment. Use 'success' for manually recorded/offline payments so linked invoices are marked paid when payment_parts cover the amount due.success
external_idNoExternal reference ID for this payment.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior4/5

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

With no annotations, description discloses backend assigns timestamp, effect of status='success' on invoice payment, and that created status is unrealized. Could mention return value or side effects, but sufficient for a mutation tool.

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

Conciseness4/5

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

Single paragraph with key points front-loaded. No wasted sentences, but could be slightly more structured for easier parsing.

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

Completeness3/5

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

Covers most aspects, but lacks description of return value (no output schema) and does not address __userContext parameter. For a complex tool with 9 params, these gaps reduce completeness.

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?

Schema coverage is 100%, but description adds value beyond schema: explains type and payment_method relationship, provides example for payment_parts, clarifies amount units. Still, some parameter descriptions in schema are already clear.

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 the tool records manual/offline payments or tax-withheld amounts, equivalent to frontend Add Payment flow. Distinguishes from sibling tools like refundPayment, payInvoice, etc.

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 specifies when to use (manual/offline payments, tax withheld) and what not to use (refunds, authorizations, reversals, etc.). Provides guidance on type, status, and payment_method usage. Includes warning about status='created' not reducing amount_due.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zenskar/mcp-zenskar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server