Skip to main content
Glama
Sign In
OpenMonetis MCP

OpenMonetis MCP

by Welington98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Pré-visualizar importação de extrato

preview_transaction_import
Read-onlyIdempotent

Preview account statement imports from OFX, CSV, or XLSX files by returning detected account/card, period, transactions, duplicates, and suggested categories without saving any data.

Instructions

Envia um arquivo de extrato (OFX, CSV ou XLSX) e retorna o que seria importado: conta/cartão detectado, período, transações com duplicatas e categoria sugerida. Nada é gravado. Aceita filePath (host do MCP) ou fileName + contentBase64.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preview_transaction_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNameNoNome do arquivo. Obrigatório apenas quando contentBase64 é usado.
filePathNoCaminho absoluto do arquivo (OFX/CSV/XLSX) no host onde o MCP roda.
contentBase64NoConteúdo do arquivo em base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds the crucial confirmation that nothing is persisted and discloses the response shape (detected account, period, duplicates, suggested category) — important since no output schema exists. It omits limits such as file size, encoding, or parse-error behavior.

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 sentences, front-loaded with the action and result, then the no-write guarantee, then the input modes. No filler, and the supported formats (OFX, CSV, XLSX) are packed parenthetically.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, three-parameter ingest tool with no output schema, the description covers the action, the returned fields, the no-persistence guarantee, and the alternative input modes. It stops short of error/limit behavior, which an agent would still need for edge cases like malformed files.

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 100%, so the baseline would be 3, but the description adds a constraint the schema cannot express: the two input modes are alternatives — `filePath` on the MCP host, OR `fileName` + `contentBase64`. With zero required parameters in the schema, this either/or guidance is genuinely load-bearing.

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 (envia/retorna pré-visualização) and resource (arquivo de extrato) and enumerates what the preview returns: detected account/card, period, transactions with duplicates, and suggested category. 'Nada é gravado' implicitly separates it from the write-side siblings such as import_transactions, though no sibling is named explicitly.

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?

The preview-only framing ('retorna o que seria importado', 'Nada é gravado') makes the intended usage apparent: inspect before committing. However, it never states when to prefer this over import_transactions, nor any preconditions (file must exist on host, supported encodings), so routing is left to inference.

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

Deploy Server

Other Tools