Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Wave: Get Invoice Payment

wave_get_invoice_payment
Read-onlyIdempotent

Retrieve a specific invoice payment by its ID. Use this to check payment details, verify status, or reconcile records without listing all payments on an invoice.

Instructions

Get one invoice payment by ID. To see every payment on an invoice, call wave_get_invoice instead: it returns them all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payment_idYesThe Wave invoice payment 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.3/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the scoping behavior (single payment vs. all payments) but does not describe edge-case behavior such as not-found handling or output specifics, which would be useful beyond the static annotations.

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 two sentences with no redundant text. The primary purpose is front-loaded, and the sibling alternative is contained in a single efficient second sentence. Every word earns its place.

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?

For a simple single-record retrieval tool with three well-documented parameters, a required ID, and annotations carrying the safety profile, the description is complete. No output schema exists, but response_format in the schema already explains what the agent will receive.

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 already documents payment_id, business_id, and response_format. The description does not add further parameter-level meaning beyond the schema, so the baseline score 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 explicitly states 'Get one invoice payment by ID', identifying both the action and resource with precision. It also differentiates from wave_get_invoice by noting that the sibling retrieves all payments on an invoice, which is especially helpful given the similar-sounding sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives direct when-to-use guidance: use this tool for a single payment by ID, and use wave_get_invoice when all payments on an invoice are needed. This explicit alternative routing removes ambiguity without requiring the agent to explore sibling schemas.

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