Skip to main content
Glama
Sign In
Wave MCP Server

Wave MCP Server

by LightningBerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_invoice_json

Retrieve a Wave invoice as structured JSON for use in data analysis, system integration, or archival purposes.

Instructions

Export Wave invoice to JSON format

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "invoiceId": "<invoiceId>"
    },
    "name": "export_invoice_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Export to JSON' implies a read-like operation but does not state side effects, output format details, authentication needs, or whether the tool returns the JSON directly or triggers a download. The description adds no behavioral context beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly worded sentence with no redundancy or filler. It is front-loaded with the action and resource, making it easy to parse, though it is quite terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description should clarify return behavior, whether this is a read-only export, and how it differs from get_invoice. It does not. For a tool with a single constrained parameter, this is still a meaningful gap in operational context.

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

Parameters2/5

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

The schema has only one parameter, invoiceId, with 0% schema description coverage. The description does not explain what invoiceId refers to, how to obtain it, or any expected format. Although the parameter name is fairly self-explanatory, the description adds no semantic value beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Export'), a resource ('Wave invoice'), and an output format ('JSON'). This clarifies the core function and distinguishes it from the sibling generate_invoice_pdf by format, though it does not explicitly differentiate it from get_invoice.

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 guidance is given about when to use this tool versus alternatives. The description does not mention any scenarios, exclusions, or sibling tools, so an agent must infer usage entirely from the tool name and one-line description.

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