OpenMonetis MCP

Anexar arquivo à transação

upload_attachment

Uploads a PDF or image file from the host to a transaction using the signed prepare → upload → confirm flow, requiring confirm set to true.

Instructions

Envia um arquivo do host (PDF ou imagem) para uma transação usando o fluxo de upload assinado: prepare → upload → confirm. 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": {
      "transactionId": "<transactionId>",
      "filePath": "<filePath>"
    },
    "name": "upload_attachment"
  }
}

Input Schema

Name	Required	Description
`confirm`	No
`filePath`	Yes	Caminho absoluto do arquivo no host do MCP.
`mimeType`	No	Detectado pela extensão quando omitido (.pdf, .jpg/.jpeg, .png, .webp).
`transactionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior, and the description adds real value on top: it discloses the three-step signed upload flow (prepare → upload → confirm) and the confirmation gate. It stops short of covering failure modes, size limits, or whether an existing attachment is replaced.

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 sentences, front-loaded with the action and resource, followed by the flow and the hard requirement. No filler.

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?

For a 4-parameter mutation tool with no output schema, the description covers the flow and the confirm gate but omits what the agent would want next: return value shape, size/type limits, and behavior when an attachment already exists.

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?

With only 50% schema coverage, the description compensates well: it clarifies that the file comes from the host, that PDF/image types are accepted (mapping to mimeType), that the target is a transaction (transactionId), and that confirm must be true. Only the exact semantics of confirm's effect are left implicit.

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 ('Envia um arquivo do host ... para uma transação') plus the accepted file types (PDF ou imagem), so the agent knows exactly what the tool does. It does not explicitly contrast with siblings like delete_attachment or get_attachment_download_url, which keeps it from a 5.

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?

Gives a concrete prerequisite ('Exige `confirm: true`') and names the internal flow, which implies when the tool is applicable. However, it offers no explicit when-not guidance or routing to alternatives such as the download-URL sibling, so usage is only implied.

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

Deploy Server