Skip to main content
Glama
Sign In
WaveQ

WaveQ

by IshaanDugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

first_edge_after

Query a VCD waveform to find the first transition edge of a specified type after a given reference time.

Instructions

Return the first edge of a given kind after a 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": {
      "signal": "<signal>",
      "kind": "<kind>",
      "time": "<time>"
    },
    "name": "first_edge_after"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesEdge kind
timeYesReference time
signalYesSignal full path or unique leaf

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
statusYes
summaryYes
confidenceNo
limitationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states a read operation but lacks any detail on side effects, authentication needs, or required permissions. The behavior beyond 'return' is opaque.

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 waste. It could be slightly more informative but remains 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 having an output schema (not provided), the description lacks details on return format, edge kinds, time format, or signal format. With three required parameters, this minimal description is insufficient for complete agent understanding.

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 description coverage is 100%, so parameters are already documented. The description adds no new meaning beyond what the schema provides, meeting the baseline for this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns the first edge of a given kind after a time. It uses a specific verb and resource, and the mention of 'first edge' distinguishes it from sibling tools like 'edges' which likely return all edges.

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 guidance is provided on when to use this tool versus alternatives such as 'edges' or 'stable_between'. The description only states what the tool does without context for selection.

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