Skip to main content
Glama
wave-av

WAVE MCP Server

Official
by wave-av

wave_get_stream_health

Get real-time health metrics like bitrate, frame rate, and latency for a specific stream. Monitor stream performance and identify issues promptly.

Instructions

Get real-time health metrics for a stream including bitrate, frame rate, and latency

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stream_idYesThe UUID of the stream to check

Implementation Reference

  • The async handler function that executes the 'wave_get_stream_health' tool logic. It calls the WAVE API endpoint /api/v1/streams/{stream_id}/health and returns the response body.
      async ({ stream_id }) => {
        const res = await waveFetch(`/api/v1/streams/${stream_id}/health`);
        if (!res.ok) return errorContent(res.status, res.body);
    
        return textContent(res.body);
      },
    );
  • Registration of the 'wave_get_stream_health' tool via server.tool(), with description and Zod schema for the stream_id parameter.
    server.tool(
      "wave_get_stream_health",
      "Get real-time health metrics for a stream including bitrate, frame rate, and latency",
      {
        stream_id: z.string().uuid().describe("The UUID of the stream to check"),
      },
      async ({ stream_id }) => {
        const res = await waveFetch(`/api/v1/streams/${stream_id}/health`);
        if (!res.ok) return errorContent(res.status, res.body);
    
        return textContent(res.body);
      },
    );
  • Zod input schema for the tool: requires a single 'stream_id' parameter as a UUID string.
    {
      stream_id: z.string().uuid().describe("The UUID of the stream to check"),
  • The waveFetch helper function used by the handler to make authenticated HTTP requests to the WAVE API.
    async function waveFetch(
      path: string,
      init?: RequestInit,
    ): Promise<{ ok: boolean; status: number; body: string }> {
      const url = `${getBaseUrl()}${path}`;
      const res = await fetch(url, {
        ...init,
        headers: {
          ...getAuthHeaders(),
          ...init?.headers,
        },
      });
      const body = await res.text();
      return { ok: res.ok, status: res.status, body };
    }
  • The errorContent helper function used to format error responses.
    function errorContent(
      status: number,
      body: string,
    ): { content: Array<{ type: "text"; text: string }> } {
      return textContent(`Error ${status}: ${body}`);
    }
Behavior3/5

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

With no annotations, the description carries the burden. It indicates a read operation returning metrics, but does not disclose details like authentication requirements, rate limits, or behavior on invalid stream IDs.

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 wasted words. It efficiently conveys the tool's purpose and key output.

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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly complete. It could mention error handling or real-time update frequency, but is sufficient for an AI agent.

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 coverage is 100% with one parameter well-described. The description adds value by listing specific metrics returned (bitrate, frame rate, latency), which is beyond the schema's parameter description.

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 clearly states the tool gets real-time health metrics (bitrate, frame rate, latency) for a stream. It distinguishes from siblings by focusing on health metrics, but does not explicitly differentiate from similar tools like wave_get_stream_metrics.

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 description implies usage when needing stream health metrics, but provides no explicit guidance on when to use this tool versus alternatives (e.g., wave_get_stream_metrics) or any prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wave-av/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server