WaveQ

Overview Schema Source Related Servers Discussions Admin

window_digest

Summarize signal changes around a specified time to identify events leading to a failure, using optional signal and scope filters.

Instructions

Summarize what changed around a time without dumping raw VCD text. Good first debug query near a failure.

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": {
      "center_time": "<center_time>",
      "radius": "<radius>"
    },
    "name": "window_digest"
  }
}

Input Schema

Name	Required	Description
`scope`	No	Optional scope filter
`radius`	Yes	Half-window radius
`signals`	No	Optional selected signals
`center_time`	Yes	Center time
`max_signals`	No	Maximum signals

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`status`	Yes
`summary`	Yes
`confidence`	No
`limitations`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Jul 13, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It states that the tool 'summarizes' and does not dump raw text, which implies a read-only summary. However, it does not detail other behaviors like side effects, authorization needs, or output specifics, leaving some gaps.

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 consists of two concise sentences with no wasted words. The first sentence states the core function, and the second provides usage context. Every sentence earns its place.

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 complexity (5 parameters, output schema exists), the description covers the main idea and usage context. It is complete enough for a first debug query, though it could mention filtering capabilities briefly. Output schema reduces the need for return value details.

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?

The input schema provides full descriptions for all parameters (100% coverage). The tool description does not repeat parameter details but adds context (summary around a time). Baseline is 3, and the description does not add significant value beyond what schema already offers.

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 clearly states 'Summarize what changed around a time', identifying the verb (summarize) and resource (what changed around a time). It distinguishes itself from 'dumping raw VCD text' and provides a use case, making it specific and helpful.

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?

The description says 'Good first debug query near a failure', which gives a clear context for usage. However, it does not explicitly mention when not to use or compare with sibling tools, so it lacks explicit alternatives.

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

Deploy Server