Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Wave: Get Customer

wave_get_customer
Read-onlyIdempotent

Retrieve a customer's complete details, including address and shipping, by supplying their Wave customer ID.

Instructions

Get one customer by ID, including address and shipping details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
customer_idYesThe Wave customer ID.
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

A3.8/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. The description adds useful return-content context ('address and shipping details') beyond the annotations, but does not disclose not-found behavior, error cases, or any other runtime characteristics. 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 front-loaded sentence with no filler words. It states the action, the target resource, the selection mechanism, and a useful output detail, earning every word.

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?

This is a low-complexity get-by-ID tool with rich annotations and 100% parameter documentation. The description tells the agent the key selection method and the included record fields, which is enough for a basic read call. It could mention not-found behavior or explicitly point to list_customers for non-ID lookup, but those are minor gaps.

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%; business_id, customer_id, and response_format are already fully documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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, resource, and lookup key: 'Get one customer by ID'. It also adds scope with 'including address and shipping details', which distinguishes it from a plain customer fetch and implies it is not the list operation (wave_list_customers).

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

Usage Guidelines3/5

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

The phrase 'by ID' implies the intended usage: use this when you already have a specific customer_id. However, it does not explicitly mention alternatives such as wave_list_customers for searching or listing, nor does it state when not to use this tool. Usage is implied rather than directly guided.

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