Skip to main content
Glama
oliverames

MCP Server for Wave

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Wave: List Vendors

wave_list_vendors
Read-onlyIdempotent

List vendors (suppliers) for a Wave business. Filter by exact email, name substring, or modification date; optionally fetch all pages.

Instructions

List vendors -- the suppliers a business buys from. Vendors are read-only in Wave's API: they can be listed and read but not created, changed, or deleted. Wave filters by exact email only; name_contains is applied locally, so pair it with fetch_all=true on a long vendor list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number for offset pagination.
emailNoExact email match, applied by Wave.
fetch_allNoWalk every page instead of returning just one. Slower, but complete.
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.
name_containsNoCase-insensitive substring match on name, applied locally.
modified_afterNoISO 8601 timestamp; only vendors changed after it.
modified_beforeNoISO 8601 timestamp; only vendors 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.2/5.0
Behavior5/5

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

The description goes beyond the readOnlyHint annotation by explicitly stating that vendors cannot be created, changed, or deleted in Wave's API. It also exposes a non-obvious behavioral trait: name_contains is applied locally, not by Wave, and therefore should be paired with fetch_all=true on long vendor lists. This is valuable context that annotations and schema alone do not provide.

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?

Three sentences, front-loaded with purpose, followed by the read-only trait and the single caveat that matters for correctness. There is no filler, repetition, or schema re-stating; every sentence 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 9-parameter list tool with no output schema, the description covers the core semantics: purpose, read-only constraint, and the non-obvious local-filter caveat. It does not give list-versus-get selection guidance or pagination defaults, but those are partly addressed by the schema and the fetch_all advice. Reasonably complete, though a pointer to wave_get_vendor would make it fully self-contained.

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 description coverage is 100%, so the baseline is 3. The description adds real param-level nuance beyond the schema: email is an 'exact email' match by Wave, name_contains is 'applied locally', and fetch_all should be paired with name_contains for complete local filtering. It does not discuss page, page_size, or business_id, but those are already well described in the schema.

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 'List vendors -- the suppliers a business buys from', giving a specific verb and resource and clarifying the domain concept. 'Vendors are read-only... listed and read' also makes clear this is a read/list operation, distinguishing it from any create/update/delete intent and from the sibling wave_get_vendor by verb and scope.

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

Usage Guidelines2/5

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

No alternative tool is referenced, so there is no explicit guidance about when to use wave_list_vendors versus wave_get_vendor or the other list tools. The only usage direction is operational ('pair it with fetch_all=true') rather than selection guidance, and prerequisites such as business_id defaulting are left to the schema.

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