Skip to main content
Glama
Sign In
wtf-wave

wtf-wave

by xtrollyj00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

command

Destructive

Execute : commands on a waveform workspace to decode protocols, add rows, place cursors, and undo edits. Answers with the rows added or removed.

Instructions

Run one of wtf's : commands on the workspace: decode, protocol, rows, cursors (help commands). Answers with the rows it added or removed; undo takes a step back.

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": {
      "line": "<line>"
    },
    "name": "command"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYesA `:` command without the colon: `decode ...`, `add top.cpu /_valid$/`, `cursor 2 80ns` (`help commands`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / line / description
      Previous value: -"A `:` command without the colon: `decode ...`, `add ...`, `cursor 2 80ns` (`help commands`)."New value: +"A `:` command without the colon: `decode ...`, `add top.cpu /_valid$/`, `cursor 2 80ns`\n(`help commands`)."
  2. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description usefully concretizes that: it 'answers with the rows it added or removed' and `undo` reverses a step. That tells an agent the blast radius is workspace rows and that recovery exists — real added context — but permissions and failure behavior are unstated.

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?

Two tight sentences, front-loaded with what the tool does, then return shape and undo. The inline list ('rows, cursors') is slightly ragged and the parenthetical help pointer is buried, but nothing is wasted.

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 single-string command dispatcher with no output schema, it covers action, return value, undo semantics, and points at `help commands` for the full verb catalog. Missing only permission/scope details for a destructive tool.

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 coverage is 100% and the schema itself documents `line` with examples, so the description adds little parameter-level meaning beyond restating the command categories. Baseline 3 applies.

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?

States a specific verb+resource: 'Run one of wtf's `:` commands on the workspace', and enumerates examples (`decode`, `protocol`, rows, cursors). An agent can tell this is a generic command dispatcher rather than a structured sibling like `records` or `values`, though it never explicitly contrasts with those.

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?

Usage is implied: run an arbitrary `:` command, with `undo` noted as a step back and `help commands` as the discovery path. There is no explicit guidance on when to prefer this dispatcher over the dedicated sibling tools (find, records, values, view).

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