Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Wave: List Products

wave_list_products
Read-onlyIdempotent

Retrieve products and services from Wave Accounting to reference in invoice and estimate line items. Filter results by name, status, or modification date.

Instructions

List products and services. Invoice and estimate line items must reference a product, so this is the usual first step when building either one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number for offset pagination.
sortNoNAME_ASC, NAME_DESC, CREATED_AT_ASC/DESC, MODIFIED_AT_ASC/DESC. Defaults to NAME_ASC.
is_soldNoOnly products sold to customers.
fetch_allNoWalk every page instead of returning just one. Slower, but complete.
is_boughtNoOnly products bought from vendors.
page_sizeNoRecords per page (1-200).
business_idNoBusiness to operate on: the base64 id from wave_list_businesses (a bare business UUID is also accepted). Defaults to the business set by wave_set_default_business. When calls may be minutes apart, pass it on every call.
is_archivedNoFilter to archived (true) or active (false) products.
name_containsNoCase-insensitive substring match on name, applied locally.
modified_afterNoISO 8601 timestamp; only products changed after it.
modified_beforeNoISO 8601 timestamp; only products changed before it.
response_formatNoOutput format: "markdown" for a compact human-readable summary, "json" for the complete record.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.8
    • changedInput schema / properties / business_id / description
      Previous value: -"Business to operate on. Defaults to the session business set by wave_set_default_business."New value: +"Business to operate on: the base64 id from wave_list_businesses (a bare business UUID is also accepted). Defaults to the business set by wave_set_default_business. When calls may be minutes apart, pass it on every call."
  2. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds domain context (products are referenced by line items) but discloses no behavioral traits like pagination defaults, local filtering, or return shape beyond what the schema already documents. Value-add is modest, consistent with annotations carrying the safety burden.

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 with zero waste: the core function is front-loaded, followed by a single high-value workflow note. Every word earns its place.

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?

For a read-only list tool with a fully self-documenting 12-parameter schema, complete annotations, and a response_format parameter controlling output, the description is nearly sufficient. It supplies the key missing context — why and when the tool matters in invoice/estimate construction. Only an explicit pointer to wave_get_product for single-record lookups is absent.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter has a meaningful description, so the schema does the heavy lifting. The description itself adds no parameter-level meaning (it mentions no filters or pagination), landing exactly at the baseline 3.

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 states a specific verb and resource ('List products and services') with no ambiguity. It is semantically distinct from the sibling wave_get_product, which is the singular retrieval counterpart, and the scope is clear enough that an agent need not open the schema to know what the tool enumerates.

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 second sentence gives clear contextual guidance: invoice and estimate line items must reference a product, so this list is 'the usual first step when building either one.' This tells the agent when the tool fits a workflow, though it does not name exclusions or explicitly route to wave_get_product when a single known product is needed.

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

Deploy Server

Other Tools