Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Confirmar item do inbox como lançamento

confirm_inbox_item

Convert a captured inbox item into a transaction. Send confirm: true to apply it; otherwise the tool returns the proposed payload for review.

Instructions

Converte um item capturado em transação. Recebe os mesmos campos de create_transaction. Exige confirm: true; sem isso devolve o payload proposto.

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": {
      "name": "<name>",
      "amount": "<amount>",
      "type": "<type>",
      "paymentMethod": "<paymentMethod>",
      "purchaseDate": "<purchaseDate>",
      "personId": "<personId>",
      "inboxItemId": "<inboxItemId>"
    },
    "name": "confirm_inbox_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
noteNo
typeYesTipo da transação. Transferências (type: 'transfer') só aceitam condition: 'single'.
amountYes
cardIdNo
tagIdsNo
confirmNo
dueDateNo
personIdYes
accountIdNo
conditionNo'single' (única, padrão), 'installment' (parcelada) ou 'recurring' (recorrente). Transferências só aceitam 'single'.single
isSettledNo
categoryIdNo
inboxItemIdYesID do item da caixa de entrada.
settledDateNo
splitSharesNoDivisão entre pessoas. A soma deve ser igual ao amount.
purchaseDateYes
invoicePeriodNoFatura do cartão (apenas crédito não recorrente).
paymentMethodYesForma de pagamento. Transferências (type: 'transfer') exigem 'bank_transfer'.
sourceAccountIdNoConta de origem, obrigatória em transferências.
installmentCountNo
startInstallmentNo
boletoPaymentDateNo
recurrenceEndDateNo
recurrenceFrequencyNo
destinationAccountIdNoConta de destino, obrigatória em transferências.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.3/5.0
Behavior4/5

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

The annotations only say the call mutates and is not idempotent. The description adds a genuinely useful behavior the schema cannot express: without confirm:true the tool performs no write and returns the proposed payload, making the dry-run safe. It omits what happens to the inbox item afterwards (consumed, archived, deleted) and whether repeated calls with confirm are safe, which are the remaining gaps for a mutating 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?

Three short sentences, front-loaded with the conversion action, then the parameter contract, then the confirm requirement. Nothing is padded. The middle sentence is efficient but leans on an external schema reference rather than self-contained detail.

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?

For a 26-parameter mutation with 7 required fields and no output schema, the definition is thin: it never explains the required-field set, the transfer-specific constraints, the shape of the proposed payload returned in dry-run mode, or the post-conversion state of the inbox item. The 'same fields as create_transaction' shorthand offloads most of the burden to a tool the agent may not have inspected.

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?

With 26 parameters and only 31% schema description coverage, the description needs to carry real weight, but it only clarifies confirm and defers the rest to 'the same fields as create_transaction' — a pointer an agent cannot resolve from this definition alone. It adds no meaning for required fields like personId, purchaseDate, or the conditional constraints on type/paymentMethod/condition that live only in enum descriptions.

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?

States a specific verb and resource: converting a captured inbox item into a transaction. It also names the sibling it mirrors (create_transaction), which lets an agent separate it from plain transaction creation. It stops short of a crisp 'use this instead of create_transaction when the record already sits in the inbox' framing.

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 only implied: the confirm gate implicitly tells the agent to call once without confirm to preview, then again with it. There is no explicit statement of when to pick this over create_transaction, suggest_inbox_item, or discard_inbox_items, and no mention of prerequisites such as the item still being pending.

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