Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Wave: Get Product

wave_get_product
Read-onlyIdempotent

Fetch a product by ID to access its accounts and default sales taxes, providing complete product details for accounting and bookkeeping.

Instructions

Get one product by ID, including its accounts and default sales taxes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYesThe Wave product ID.
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.
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, so the safety profile is covered by structured data. The description adds the useful detail that the response includes accounts and default sales taxes, but does not disclose other behavioral traits. This is adequate but not rich.

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 a single, tight sentence with no wasted words. The core purpose and the key response inclusions are front-loaded, making it easy to scan.

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 simple read-only getter with all parameters fully documented in the schema and annotations carrying the behavioral safety profile, the description is complete enough. It even hints at response contents, which partially compensates for the absence of an output schema. Minor gaps like error handling are not critical for this tool type.

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%, so the schema fully documents all three parameters. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 ('Get'), a specific resource ('one product by ID'), and adds the distinguishing detail that the result includes accounts and default sales taxes. This clearly differentiates it from a list operation like wave_list_products.

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 phrase 'by ID' gives clear context that this tool is for fetching a single known product, rather than listing products. It does not explicitly name an alternative or exclusion, but the intended usage is unambiguous enough for an agent.

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