Skip to main content
Glama
guipmilek

Despezzas MCP

by guipmilek

Preparar Criação de Transação

despezzas_prepare_create_transaction
Read-only

Preview, assemble, and validate a new transaction payload before sending it to Despezzas.

Instructions

Auxiliar de pré-visualização. Monta e valida o payload de uma nova transação sem chamar o Despezzas. Use antes de despezzas_create_transaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
kindNoexpense
paidNo
titleYes
frequencyNo
account_idNo
amount_modeNoper_installment
category_idNo
descriptionNo
amount_centsYesValor em centavos. Exemplo: 12345 = R$123.45.
installmentsNo
credit_card_idNo
subcategory_idNo
transaction_typeNounique
allow_uncategorizedNoDefina como true apenas quando quiser intencionalmente criar uma transação sem category_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
readyYes
issuesYes
methodYes
payloadYes
endpointYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, and description reinforces that it does not call the API, adding context. However, it does not detail what the output contains (e.g., validated payload or errors), leaving some behavioral gaps.

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: first defines the tool as a preview assistant, second gives usage instruction. No unnecessary words, front-loaded with purpose.

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?

Given the tool's complexity (15 parameters, many enums, output schema present), the description is minimal. It does not explain validation behavior or output details, though output schema partially compensates.

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?

Schema description coverage is only 13% and the description does not describe any parameters. It relies on parameter names and schema descriptions, which are incomplete. With low coverage, description should compensate but does not.

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?

Description clearly states it's a preview assistant that builds/validates transaction payload without calling Despezzas. It differentiates from siblings by specifying it's for preparation before creation, and there are similar prepare tools for update and delete.

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 says 'Use antes de despezzas_create_transaction', indicating when to use it. It implies it's for preview before actual creation, but does not provide explicit when-not-to-use scenarios or alternatives.

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