Skip to main content
Glama

mark_invoice_paid

Marks a specified WeFact invoice as paid, optionally recording the payment date and method.

Instructions

Mark an invoice as paid.

Args: invoice_code: e.g. '202401001'. pay_date: ISO date. Defaults to today. payment_method: WeFact code, e.g. 'wire' for bank transfer ('banktransfer' is rejected as an invalid payment method).

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_code": "<invoice_code>"
    },
    "name": "mark_invoice_paid"
  }
}

Input Schema

NameRequiredDescriptionDefault
pay_dateNo
invoice_codeYes
payment_methodNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose one genuinely useful trait: a specific invalid payment_method value. It says nothing about idempotency when the invoice is already paid, whether debtor balances are updated, or whether the change is reversible — important omissions 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.

Conciseness5/5

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

The action statement is front-loaded in one line, followed by a compact per-argument list. Every sentence carries information; nothing is redundant or padded.

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?

An output schema exists, so return values need not be described, and the parameter documentation is thorough. For a no-annotation mutation tool, however, the definition lacks the safety and side-effect context an agent needs to invoke it confidently on a live financial record.

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 0%, so the description is the only documentation, and it compensates well: an example invoice_code format, ISO format plus 'defaults to today' for pay_date, and a WeFact code example plus a rejected value for payment_method. It stops short of listing valid payment_method codes, so the agent still must guess the acceptable enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Mark an invoice as paid') that is unambiguous and instantly distinguishable from read siblings like get_invoice or list_invoices. It does not, however, contrast itself with adjacent mutation siblings such as credit_invoice, leaving the agent to infer the boundary.

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?

Usage is strongly implied by the name and first line, and the payment_method note gives a concrete do/don't ('banktransfer' is rejected). There is no explicit statement of when to prefer this over credit_invoice or what preconditions must hold (e.g. invoice must be open/unpaid), so guidance remains implied rather than stated.

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