Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames

Wave: List Accounts

wave_list_accounts
Read-onlyIdempotent

List chart of accounts with balances. Filter by type (EXPENSE, INCOME, ASSET, LIABILITY) and subtype (e.g., CASH_AND_BANK, CREDIT_CARD) to find the correct account for transactions.

Instructions

List the chart of accounts, with balances. Filter by type to find the account a transaction needs: EXPENSE for expense categories, INCOME for revenue, ASSET with subtype CASH_AND_BANK for bank accounts, LIABILITY with subtype CREDIT_CARD for cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number for offset pagination.
typesNoFilter by type: ASSET, LIABILITY, EQUITY, INCOME, EXPENSE.
subtypesNoFilter by subtype, e.g. ["CASH_AND_BANK", "CREDIT_CARD"].
fetch_allNoWalk every page instead of returning just one. Slower, but complete.
page_sizeNoRecords per page (1-200).
business_idNoBusiness to operate on. Defaults to the session business set by wave_set_default_business.
is_archivedNoFilter to archived (true) or active (false) accounts.
response_formatNoOutput format: "markdown" for a compact human-readable summary, "json" for the complete record.markdown
excluded_subtypesNoSubtypes to omit.
Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive behavior, which is consistent. The description adds transparency by mentioning balances in output, pagination parameters, and default business behavior. 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?

The description is extremely concise—two sentences front-loading the core function and then providing filtering examples. No unnecessary words.

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?

Despite 9 parameters and no output schema, the description covers the main return content (list with balances) and key behaviors (pagination, filtering). It is sufficient for an agent to understand and invoke the tool correctly.

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% with descriptions for all 9 parameters. The description adds practical guidance by showing how to filter for specific account categories, going beyond the schema. This extra value justifies a score above baseline.

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 the tool lists the chart of accounts with balances. It distinguishes from siblings like wave_get_account by focusing on listing and filtering, and provides specific type examples, making its purpose unmistakable.

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?

The description gives explicit guidance on when to use this tool—to find accounts for transactions based on type/subtype. It includes concrete examples but does not explicitly state when not to use it or mention alternatives, though siblings imply them.

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

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