Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wave_get_usage

Retrieve billed usage for a date range, defaulting to the current month. Specify optional start and end dates to get usage details.

Instructions

Get billed usage for a date range (GET /v1/billing/usage), defaulting to the current month

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoRange end (YYYY-MM-DD), default: today
fromNoRange start (YYYY-MM-DD), default: start of current month

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / breakdown
      Removed value: -{
-  "description": "Level of usage detail (default: summary)",
-  "enum": [
-    "summary",
-    "daily",
-    "by_stream"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Range start (YYYY-MM-DD), default: start of current month",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • removedInput schema / properties / period
      Removed value: -{
-  "description": "Billing period to query (default: current)",
-  "enum": [
-    "current",
-    "previous"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Range end (YYYY-MM-DD), default: today",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  2. First observedv0.1.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals the HTTP GET method, implying a read-only operation, and mentions the default current-month behavior. However, it does not describe authentication needs, response contents, timezone handling, or whether the usage data is aggregated or itemized.

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 that names the operation, resource, endpoint, and default behavior without any wasted words. It is immediately scannable and easy to parse.

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 tool with two optional and fully documented parameters, the description is largely sufficient. The only gap is that there is no output schema and the description does not clarify what the response looks like, but this does not block correct invocation.

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%, with both `from` and `to` documented including defaults and date format. The description's 'defaulting to the current month' restates what the schema already says, adding no new parameter semantics beyond the endpoint context.

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 clearly identifies the operation as retrieving billed usage for a date range, with a specific endpoint and a default behavior. It distinguishes itself from siblings like wave_get_subscription and wave_get_viewers by naming a unique billing resource.

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 description gives clear context for when to use this tool: when billed usage data for a date range is needed, and it notes that omitting dates defaults to the current month. It does not explicitly name alternatives or exclusion conditions, but no sibling is a direct substitute.

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