Skip to main content
Glama
Sign In
wtf-wave

wtf-wave

by xtrollyj00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

render

Idempotent

Draw signals over a time range as text, matching wtf's screen output; with no signals listed, render the workspace instead.

Instructions

Draw signals over a time range as text, as wtf's screen does; without signals, the workspace.

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": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the range; default the end, or the workspace's range.
fromNoStart of the range; default the start, or the workspace's range.
unitNoThe unit of the range in the heading, `ns`, `us` (`help times`).
widthNoWidth in characters; default 120.
signalsNoSignals drawn top to bottom; none: the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / to / description
      Previous value: -"End of the time range shown."New value: +"End of the range; default the end, or the workspace's range."
    • changedInput schema / properties / unit / description
      Previous value: -"The unit of the range in the heading; as for `values`."New value: +"The unit of the range in the heading, `ns`, `us` (`help times`)."
  2. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (idempotent, non-destructive, closed-world). The description adds that output is a textual approximation of a terminal screen and that omitting signals falls back to the workspace, which is genuine context beyond the annotations, but it says nothing about how large the output is, truncation, or formatting limits.

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?

A single front-loaded sentence with no filler; the semicolon cleanly separates the default case. The brevity comes at the cost of a cryptic reference ("wtf's screen") that the reader must already understand.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining what the rendered text looks like, yet it only says "as text, as wtf's screen does". For a rendering tool with five optional parameters, that leaves the agent guessing about output shape and size.

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%, so the schema already documents all five parameters including defaults. The description restates only the signals fallback, which the schema's signals description already says ("none: the workspace"), so it adds essentially no new meaning beyond structured fields.

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?

"Draw signals over a time range as text" gives a specific verb (draw/render) and resource (signals over a range), and the trailing clause distinguishes the no-signals case as the workspace. The phrase "as wtf's screen does" is insider jargon that assumes knowledge of an external UI, which blunts the clarity slightly.

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 only implied: you call this when you want a textual picture of signals. There is a useful conditional ("without signals, the workspace") that tells the agent the empty-input behavior, but nothing states when to prefer this over siblings like view or present.

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