Freelance deposit and payment schedule for AI assistants
Scored across 12 tools
Each tool targets a distinct step in the deposit-schedule lifecycle, with descriptions that explicitly separate draft edits, suggestions, acceptance, and final commitment. The main potential overlap is between direct mutation tools (e.g. waive_deposit, mark_deposit_paid, record_deposit) and their suggested-change counterparts, but the approval-guard language makes the boundaries clear enough for an agent to choose correctly.
All names use snake_case and nearly all follow a verb_noun pattern (e.g. start_schedule, read_schedule, commit_schedule, waive_deposit). The naming is predictable throughout, with no mixed conventions or ambiguous abbreviations.
With 12 tools, the set is well-scoped for a deposit scheduling workflow that includes creation, reading, listing, multiple draft mutations, client-facing script control, suggestions, acceptance, and final approval. Each tool corresponds to a necessary operation or state transition in that workflow.
The surface covers the core lifecycle well: create/read/list schedules, edit deposit details, add or move payments, waive or mark the deposit paid, manage client scripts, suggest changes, accept changes, and commit the schedule. Minor gaps remain, such as cancelling or deleting a schedule or removing a later payment directly, but these are not central to the main approved-schedule workflow.
Apply one suggested schedule change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path that may waive the deposit, mark it paid, or move a payment date. Calling it is not a substitute for the freelancer's approval.
Inputs: changeId (required), confirmed (required), scheduleId (required). Returns: data
Add one later payment: a label, an amount in whole minor units, and a payment date. After the schedule is approved, a new later payment is refused until accept_schedule_change applies an add_later_payment suggestion.
Inputs: dueOn (required), label (required), scheduleId (required), amountMinor (required). Returns: data
Mark the current draft as the approved schedule. Pass confirmed true only after the freelancer explicitly approves the deposit, the later payment dates, and what the assistant may tell the client.
Inputs: confirmed (required), scheduleId (required). Returns: data
List the signed-in freelancer's deposit schedules. Use a returned id with read_schedule. Do not guess a schedule.
Inputs: offset. Returns: data
Mark the deposit paid. After the schedule is approved, marking it paid is refused until accept_schedule_change applies a mark_deposit_paid suggestion. Do not tell the client the deposit is paid unless the record already says so.
Inputs: scheduleId (required). Returns: data
Move a payment date. target deposit moves the deposit date. target later moves one later payment and requires paymentId. After the schedule is approved, a different date is refused until accept_schedule_change applies a move_payment_date suggestion.
Inputs: dueOn (required), target (required), scheduleId (required), paymentId. Returns: data
Read the schedule before answering. Quote only this record. mayTellClient and clientScript are what the assistant may tell the client. Draft status is not an approved commitment. Proposed changes do not authorize a waiver, a paid deposit, or a new payment date.
Inputs: scheduleId (required). Returns: data
Record the deposit amount in whole minor units and the deposit date as YYYY-MM-DD. This does not waive the deposit and does not mark it paid. After the schedule is approved, a different amount or date is refused until an accepted schedule change.
Inputs: dueOn (required), scheduleId (required), amountMinor (required). Returns: data
Start a draft deposit schedule for one client project. Draft figures are not an approved commitment until commit_schedule. Currency is a three-letter code. Amounts later are minor units of that currency and are the freelancer's figures.
Inputs: currency (required), reference (required), clientName (required), projectTitle (required). Returns: data
Record a suggested change. This does not change the schedule. kind waive_deposit and kind mark_deposit_paid need only a summary. kind move_payment_date requires dueOn and target; target later also requires paymentId. kind revise_deposit requires amountMinor. kind add_later_payment requires label, amountMinor, and dueOn. kind revise_client_script requires script.
Inputs: kind (required), summary (required), scheduleId (required), dueOn, +5 more. Returns: data
Waive the deposit. After the schedule is approved, waiving is refused until accept_schedule_change applies a waive_deposit suggestion. Do not tell the client the deposit is waived unless the record already says so.
Inputs: scheduleId (required). Returns: data
Record what the assistant may tell the client about the deposit and payment dates. After the schedule is approved, different wording is refused until an accepted revise_client_script suggestion. The assistant must not go beyond this script and the facts in read_schedule.
Inputs: script (required), scheduleId (required). Returns: data
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Freelance invoice line items, rates, due dates, and late terms for AI assistants
Freelance project milestones and acceptance criteria for AI assistants
Freelance scope of work, rates, deadlines, and change orders for AI assistants
Free client billing for AI assistants: hours, expenses, timers, invoices and payments.
Add one secure layer between your agents and this server.
