Skip to main content
Glama
Sign In
wtf-wave

wtf-wave

by xtrollyj00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

values

Read-only

Retrieve signal samples and change points over a specified start-to-end time range, including struct or array fields, to inspect waveform behavior.

Instructions

Values of signals from from to to: the value at from, then each change, as time value lines; omit to for one time. A struct or array also lists its fields. For when something happens, find.

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": {
      "signals": "<signals>",
      "from": "<from>"
    },
    "name": "values"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd time, inclusive; omit for the value at `from` alone.
fromYesStart time with its unit, any unit: `120ns`, `3.4ms` (`help times`).
unitNoThe unit of the answer's times (`help times`).
radixNohex, bin, dec, ... (`help radix`); `data:dec` for one signal.
signalsYesSignals by path or path end (`help names`); `signals` finds them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • changedInput schema / properties / from / description
      Previous value: -"Start time with a unit (`help times`)."New value: +"Start time with its unit, any unit: `120ns`, `3.4ms` (`help times`)."
    • changedInput schema / properties / signals / description
      Previous value: -"Signals by path or path end (`help names`)."New value: +"Signals by path or path end (`help names`); `signals` finds them."
    • changedInput schema / properties / to / description
      Previous value: -"End time, inclusive."New value: +"End time, inclusive; omit for the value at `from` alone."
    • changedInput schema / properties / to / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "signals",
-  "from",
-  "to"
-]New value: +[
+  "signals",
+  "from"
+]
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already mark this as read-only and closed-world, while the description adds that output consists of `time value` lines starting at `from`, listing each change, and that structs or arrays list their fields. With no output schema, this output-shape detail is valuable, though it does not cover edge cases such as missing signals.

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 compact and front-loaded with the core behavior. The `find` routing sentence and the struct/array note are functional rather than filler.

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?

Because there is no output schema, the description appropriately explains the returned `time value` format and distinguishes a single time from a range. It is nearly complete for this query tool, with only minor gaps around error or no-match behavior.

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%, so all five parameters are documented in the input schema. The description reinforces the `from`/`to` range semantics and `to` omission but adds little about `unit`, `radix`, or signal path interpretation beyond the schema.

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 opens with 'Values of signals from `from` to `to`', naming a specific resource and operation, then specifies the value at `from` followed by each change. It distinguishes this from the sibling `find` by ending with 'For when something happens, `find`.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete selection rules: omit `to` for a single time, and use `find` when the question is about when something happens. It also points to `signals` for finding signal names, covering adjacent alternatives explicitly.

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