Skip to main content
Glama

embedded-eda

logic_trace_decode_wavedrom

Decode .vcd waveforms or logic-analyzer .csv traces into UART 8N1, I2C, or SPI protocol frames and generate WaveDrom JSON + publication SVG timing diagrams.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "logic_trace_decode_wavedrom"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw .vcd or .csv digital trace content.
filePathNo
protocolNouart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the two output artifacts, which is genuinely useful, but says nothing about side effects (whether an SVG/JSON file is written to disk or returned inline), size or rate limits on traces, or what happens on an undecodable/malformed capture. For a converter with zero annotation coverage, these are material omissions.

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 dense sentence that front-loads the decode action and terminates with the produced artifacts. Every clause (input formats, protocol set, output types) carries distinct information with no filler.

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?

With no output schema, the description correctly names the returned artifacts, which covers the return-value question. However, for a three-parameter tool with an undocumented filePath and two mutually overlapping input channels, the definition leaves the agent without enough to call it correctly in the file-based case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: only 'text' is documented. 'filePath' has no description anywhere, and the description never clarifies whether it is an alternative to 'text', which one takes precedence when both are supplied, or whether frames are written there. The description does not compensate for the coverage gap despite that being the ambiguity most likely to cause a failed call.

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 opens with a specific verb ('Decode') applied to named resources ('.vcd waveforms or logic-analyzer .csv traces'), enumerates the supported protocols (UART 8N1, I2C, SPI), and states both artifacts produced (WaveDrom JSON and SVG timing diagrams). No sibling tool in the list performs trace-to-protocol decoding, so the scope is unambiguous.

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 input/output formats imply when to reach for this tool (you have a digital trace and want protocol frames or timing diagrams), but there is no explicit when-to-use statement, no guidance on when to prefer another tool, and no stated prerequisites. Usage is inferred rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources