Skip to main content
Glama
guipmilek

Despezzas MCP

by guipmilek

Editar Transações em Lote

despezzas_batch_update_transactions
Destructive

Preview and then apply batch updates to multiple Despezzas transactions. First call without confirm to inspect payloads, then repeat with confirm:true to commit.

Instructions

Operação de escrita. Pré-visualiza e depois edita várias transações do Despezzas com uma chamada confirm:true. Exige confirm: true. Chame uma vez sem confirm para inspecionar os payloads; repita com confirm:true apenas depois de verificar cada id e payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
updatesYesEdições de transação. Cada item usa os mesmos campos de despezzas_update_transaction, incluindo id.
stop_on_errorNoPara após o primeiro erro de API. A validação sempre roda para todos os itens antes de qualquer escrita.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
totalYes
previewYes
resultsNo
all_readyYes
confirmedYes
ready_countYes
updated_countNo
requires_confirmNo
Behavior5/5

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

Annotations provide destructiveHint: true, and the description adds behavioral details about the two-phase commit pattern, inspection of payloads, and validation before writing (from schema). No contradictions.

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?

Very concise, front-loaded with 'Operação de escrita.' Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

Given the tool's complexity, the description covers the essential workflow for batch updates with preview. Output schema exists, so return values are not needed. Complete for agent use.

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?

The description explains the workflow for confirm parameter, and the schema describes updates and stop_on_error. Adds value beyond schema by explaining preview and confirm semantics.

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

Purpose5/5

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

The description clearly states it is a write operation for editing multiple transactions, with a two-step process using confirm. It distinguishes from sibling single-update tools by emphasizing batch editing and preview.

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

Usage Guidelines4/5

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

Explicitly instructs to call without confirm for preview and with confirm only after verifying payloads. Lacks explicit alternatives or when-not-to-use, but the context sufficiently guides usage.

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/guipmilek/despezzas-mcp-clean-snapshot'

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