Skip to main content
Glama
Sign In
WaveQ

WaveQ

by IshaanDugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

define_clock

Define a clock signal by selecting a signal and an edge type to create a cycle index, enabling subsequent cycle-based waveform queries.

Instructions

Build a cycle index from one signal's edge events. Call before cycle-based tools.

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": {
      "signal": "<signal>"
    },
    "name": "define_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeNorise or fall; default rise
signalYesClock signal

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
statusYes
summaryYes
confidenceNo
limitationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

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 carry full burden. It reveals the tool is a setup step affecting subsequent cycle tools, but lacks details on whether the index is reusable, if it overwrites, or any side effects.

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?

Two sentences, front-loaded with the main purpose, no wasted words. Perfectly sized for quick comprehension.

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?

Output schema exists, so return values need not be explained. The description is complete for a simple setup tool, though it could mention whether calling it again replaces the index.

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 both parameters are already described in the schema. The description adds no extra meaning beyond what the schema provides, landing at baseline 3.

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 builds a cycle index from one signal's edge events, and distinguishes it as a prerequisite for cycle-based tools among the 17 siblings.

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?

Explicitly states 'Call before cycle-based tools,' providing clear when-to-use guidance. However, it does not mention when not to use or alternatives.

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