Tradify MCP server

Overview Schema Source Related Servers Discussions Admin

Record payment

record_payment

Records a payment received against an approved invoice, reduces the amount due, and marks the invoice paid when fully settled.

Instructions

Record a payment received against an invoice and reduce the amount due.

Adds a payment you already received to an approved invoice, as Add Payment does: amount, date, method (by name, from Settings > Payment Methods) and a reference. It charges nobody and emails nobody. The amount cannot exceed what is due; paying it all marks the invoice paid. If an accounting app is connected, Tradify syncs the payment to it.

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": {
      "invoice_id": "<invoice_id>",
      "amount": "<amount>"
    },
    "name": "record_payment"
  }
}

Input Schema

Name	Required	Description
`date`	No	Payment date. Default: today.
`amount`	Yes	Amount received, at most the amount due.
`method`	No	Payment method name, e.g. Bank Deposit, Cash, Credit Card. Default: Unknown.
`reference`	No	e.g. the check number.
`invoice_id`	Yes	Invoice ID from list_invoices.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well past the annotations: no charge is made, no email is sent, the amount is capped at the amount due, full payment flips the invoice to paid, and payments sync to a connected accounting app (which explains openWorldHint). This tells the agent exactly what side effects to expect from a non-idempotent mutation.

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 tight paragraphs: the first states the action and effect, the second supplies preconditions, limits and side effects. Every sentence carries information and the summary line is front-loaded.

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 mutation tool with no output schema, the description covers preconditions, amount constraints, downstream state changes and external sync. Combined with annotations that already declare safety and idempotency, an agent has everything needed to call it correctly.

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%, so all five parameters are already documented including defaults and the invoice_id provenance. The description echoes amount, date, method and reference without adding format or constraint detail beyond what the schema states, so the baseline 3 applies.

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?

Names a specific verb and resource ('Record a payment received against an invoice') and states the resulting state change ('reduce the amount due'). No sibling tool touches payments, so the boundary is unambiguous from the sentence alone.

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

Usage Guidelines4/5

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

Establishes the precondition explicitly - the payment must already be received and the invoice must be approved - and clarifies scope with 'It charges nobody and emails nobody', which implicitly routes charging/notifying to tools like send_invoice. It does not name an alternative tool directly, so it stops short of a 5.

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