Skip to main content
Glama
SamuelMoraesF

io.github.SamuelMoraesF/mcp-organizze

updateTransaction

Update existing Organizze transaction details like description, amount, date, and category. For recurring transactions, update all occurrences or this and future ones.

Instructions

Atualizar movimentação

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
update_allNoAtualizar todas as ocorrências (se recorrente)
update_futureNoAtualizar esta e as próximas ocorrências (se recorrente)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
dateNo
paidNo
tagsNo
notesNo
recurringNo
account_idNo
contact_idNo
created_atNo
updated_atNo
attachmentsNo
category_idNo
descriptionNo
installmentNo
account_typeNo
amount_centsNo
recurrence_idNo
credit_card_idNo
attachments_countNo
oposite_account_idNo
total_installmentsNo
paid_credit_card_idNo
credit_card_invoice_idNo
oposite_transaction_idNo
paid_credit_card_invoice_idNo
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states that the tool updates a transaction, revealing nothing about side effects, permission requirements, or impacts on recurring occurrences. For a mutation tool, this is a critical omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely brief, but it is under-specified rather than appropriately concise. It consists of a single phrase with no structure or elaboration, missing the opportunity to provide useful, organized information for the agent.

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

Completeness1/5

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

Given the tool's complexity (3 parameters, a detailed input schema with recurrence and installments attributes), the description is completely inadequate. It does not explain the effects of updating a transaction (e.g., whether recurring instances are affected), and with no annotations, the agent is left without essential context for safe and correct usage.

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?

The description does not mention any parameters, despite the schema having 3 parameters (id, update_all, update_future) with 67% of them described in the schema. It adds no semantic value beyond what is already in the schema, failing to clarify the meaning of id or how update_all and update_future affect behavior.

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

Purpose2/5

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

The description 'Atualizar movimentação' is essentially a Portuguese translation of the tool name, restating it without any additional specificity. It does not describe what a transaction update entails or how it differs from other update tools like updateAccount or updateTransfer.

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?

No guidance is provided on when to use this tool versus alternative update tools. The description gives no context about typical use cases, prerequisites, or conditions that would make this the appropriate choice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SamuelMoraesF/mcp-organizze'

If you have feedback or need assistance with the MCP directory API, please join our Discord server