Skip to main content
Glama
Sign In
WaveQ

WaveQ

by IshaanDugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

time_to_cycle

Map any timestamp to the latest clock cycle at or before that time, using a specified clock signal and edge. Helps align signal events with clock cycles in VCD waveform analysis.

Instructions

Map a time to the latest clock cycle at or before that time.

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": {
      "clock": "<clock>",
      "time": "<time>"
    },
    "name": "time_to_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeNorise or fall; default rise
timeYesQuery time
clockYesClock signal

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
statusYes
summaryYes
confidenceNo
limitationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.2/5.0
Behavior2/5

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

The description discloses the mapping direction ('latest clock cycle at or before that time') but does not explain the role of the 'edge' parameter, default behavior, or what happens for edge cases (e.g., time before the first cycle). No annotations are provided, so the description carries the full burden.

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?

The description is a single concise sentence with no redundancy. It is appropriately front-loaded, though a slightly longer description could add value without becoming verbose.

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?

Given the existence of an output schema and the tool's simplicity, the description adequately covers the basic mapping. However, it lacks details on edge conditions and parameter interactions, making it minimally complete.

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% with each parameter documented. The description adds clarifying context about the result's timing relation to the input time, providing marginal value beyond the schema definitions.

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 the tool's function: mapping a time to the latest clock cycle at or before that time. It uses a specific verb ('Map') and resource ('clock cycle'), and its relationship to the sibling 'cycle_to_time' is implied.

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

Usage Guidelines2/5

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

No explicit guidance on when to use or avoid this tool compared to siblings like 'first_edge_after' or 'cycle_to_time'. The description does not mention prerequisites or typical use cases.

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