Skip to main content
Glama
Sign In
wtf-wave

wtf-wave

by xtrollyj00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

view

Read-only

Describes the current waveform workspace in words, including rows, cursor timing, and visible range, so you can inspect the user's window without rendered graphics.

Instructions

Describe the workspace in words: rows, cursors with the time between them, visible range. Drawn: render; the user's window: user_view.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "view"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoThe unit of the answer's times, `ns`, `us` (`help times`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / unit / description
      Previous value: -"As for `values`."New value: +"The unit of the answer's times, `ns`, `us` (`help times`)."
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare a read-only, closed-world operation, so the safety profile is covered. The description adds useful detail about what the textual answer contains: rows, cursors with time between them, and visible range. It does not describe the exact output format or any edge-case behavior, so it adds only moderate behavioral context.

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 definition is compact and front-loads the core action before naming alternatives. The second sentence is telegraphic but efficient. Minor clarity loss comes from the fragmentary phrasing rather than wasted content.

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 one optional parameter, a 100%-covered schema, and no output schema, the description covers purpose, returned content, and sibling routing adequately. It could say more about the exact textual response shape, but the essentials are present.

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%, and the single optional `unit` parameter is documented in the schema as `ns` or `us`. The description adds no parameter semantics beyond what the schema already provides. The baseline score of 3 is appropriate when the schema carries the parameter documentation.

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 action: produce a verbal description of the workspace, including rows, cursors with inter-cursor time, and visible range. It also distinguishes the tool from `render` and `user_view`. The purpose is clear, though the generic name `view` and the domain term "workspace" keep it from being maximally self-explanatory.

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?

It routes the agent away from this tool when a drawn output is needed (`render`) or when the user's window is wanted (`user_view`). That gives clear alternative selection context. It does not explicitly state exclusions or prerequisites, so it stops short of full when/when-not guidance.

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