OpenMonetis MCP

Registrar acerto com pessoa

create_person_settlement

Records a payment received from a person, requiring explicit confirmation and the person ID, amount, and received date.

Instructions

Registra um acerto (recebimento) de uma pessoa. Exige confirm: true.

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": {
      "personId": "<personId>",
      "amount": "<amount>",
      "receivedAt": "<receivedAt>"
    },
    "name": "create_person_settlement"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No
`amount`	Yes
`confirm`	No
`personId`	Yes
`receivedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Nov 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds one genuinely useful behavioral fact: the call requires `confirm: true`, which is a safeguard the agent must satisfy. It stops short of saying what the write affects (e.g. person balance, ledger entries) or whether repeats create duplicates despite idempotentHint=false.

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?

Two short sentences, front-loaded with the core action and followed by the hard requirement. There is no filler, though the extreme brevity is what leaves the semantic gaps noted elsewhere.

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?

This is a financial-record mutation with no output schema and zero documented parameters; the description should carry more of that burden. It omits what is created, what it affects, and how the required fields must be interpreted, leaving an agent under-informed before a consequential write.

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 0% for five parameters, so the schema supplies types and constraints only. The description mentions just the confirm flag; it never explains personId, amount (currency/units), receivedAt (settlement date semantics), or note, leaving the required fields' meaning to inference.

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 names a specific verb and resource: 'Registra um acerto (recebimento) de uma pessoa', which tells an agent this creates a settlement/receipt record tied to a person. It does not, however, differentiate itself from siblings such as create_transaction or add_invoice_payment, which could plausibly record similar inflows.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus creating a transaction or registering an invoice payment, nor any stated preconditions beyond the confirm flag. The agent must infer the selection criteria from the name alone.

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

Deploy Server