WaveQ

by IshaanDugar

Overview Schema Source Related Servers Discussions Admin

Python

Local

values_at_cycle

Batch query values of multiple signals at a specified clock cycle from VCD waveform data.

Instructions

Batch values_at for several signals at a clock cycle.

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>",
      "clock": "<clock>",
      "cycle_index": "<cycle_index>"
    },
    "name": "values_at_cycle"
  }
}

Input Schema

Name	Required	Description
`edge`	No	rise or fall; default rise
`clock`	Yes	Clock signal
`signals`	Yes	Signal full paths or unique leaf names
`cycle_index`	Yes	Cycle index

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

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like default edge value, error handling, or side effects. The description is minimal and carries the full burden, which it fails to meet.

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?

A single sentence that conveys the core function without any unnecessary words or fluff. Front-loaded and efficient.

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

Completeness2/5

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

Despite high schema coverage and the presence of an output schema, the description lacks key behavioral details such as the default edge setting and the format of the return value. It is too brief for a batch tool with multiple parameters.

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 each parameter has a description in the schema. The tool description adds no additional meaning beyond the schema, achieving the baseline.

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?

Description clearly states 'Batch values_at for several signals at a clock cycle', using a specific verb ('batch') and resource ('signals at a clock cycle'). This distinguishes it from sibling tools like 'value_at' (single signal) and 'values_at' (batch without cycle context).

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?

The description implies usage for batch retrieval at a clock cycle but provides no explicit guidance on when to use this tool versus alternatives like 'value_at' or 'values_at'.

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

Deploy Server