Skip to main content
Glama
hvkshetry

Wave MCP Server

by hvkshetry

transaction

Destructive

Manage invoices and money transactions in Wave accounting, including creation, updates, payments, and searching.

Instructions

Invoice and money transaction management in Wave.

Entity types: invoice, money_transaction

Invoice operations: Read: list, get, search Write: create, update, delete, clone, send, approve, mark_sent, create_payment

Money transaction operations: Write: create, bulk_create (BETA — create only, no list/get/update/delete)

Args: operation: One of the operations listed above. entity_type: One of: invoice, money_transaction. entity_id: Transaction ID (base64 string, required for get/update/delete/clone/send/approve/mark_sent). data: Dict of fields for create/update. Invoice create: customerId, items (list of {productId, description, quantity, unitPrice, accountId}), invoiceDate, dueDate, memo, currency Invoice create_payment: invoiceId, paymentAccountId, amount, paymentDate, paymentMethod (BANK_TRANSFER|CASH|CHEQUE|CREDIT_CARD|OTHER|PAY_PAL), memo Money transaction create: anchor (dict with accountId, amount, direction: DEPOSIT|WITHDRAWAL), lineItems (list of {accountId, amount, balance}), externalId, description Money transaction bulk_create: transactions (list of individual create inputs) query: Search text for search operation (matches invoiceNumber, customer name, memo). page: Page number (default 1). page_size: Results per page (default 50).

Returns: JSON string with transaction data or {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
pageNo
queryNo
entity_idNo
operationYes
page_sizeNo
entity_typeNoinvoice

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond annotations, the description notes BETA status for bulk_create, lists all operations (including destructive ones), and explains parameter requirements. This adds useful context about behavior and limitations.

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

Conciseness4/5

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

The description is well-structured with sections for entity types, operations, args, and returns. It is fairly concise given the complexity, though some redundancy could be trimmed.

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?

The description covers most aspects of the tool, including all parameters and operation-specific details. The return format is only briefly mentioned, but overall it is sufficiently complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by detailing each parameter, including nested fields for data, operations, and entity types. This adds significant meaning beyond the bare schema.

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 that the tool manages 'Invoice and money transaction management in Wave' and lists specific entity types and operations. This distinguishes it from sibling tools like 'account' or 'report'.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It lists operations but lacks context about when not to use it or how it compares to siblings.

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/hvkshetry/wave-mcp'

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