hwcontract

check_serial

Capture serial output for a specified duration and validate the log against a contract's expect/forbid patterns, returning a clear pass or fail verdict.

Instructions

Read a serial port for N seconds AND judge its log against a contract's expect/forbid patterns.

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": {
      "contract_path": "<contract_path>",
      "port": "<port>"
    },
    "name": "check_serial"
  }
}

Input Schema

Name	Required	Description	Default
`baud`	No
`port`	Yes
`seconds`	No
`contract_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 31, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions reading for N seconds and judging, but omits critical details such as blocking behavior, return format, pass/fail semantics, or any side effects. This is a significant transparency gap for a hardware-interfacing tool.

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?

The description is a single concise sentence with no filler. The core action ('Read a serial port') is front-loaded, and the compound purpose is communicated efficiently.

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?

Given the tool has no annotations, no output schema, and 0% parameter documentation, the description is too sparse. It fails to specify return values, error behavior, or how the contract 'judgment' is reported, leaving the agent without enough context for reliable invocation.

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 0%, so the description must compensate. It indirectly clarifies 'port', 'seconds', and 'contract_path' but completely ignores 'baud', which is a necessary serial configuration parameter. The partial coverage leaves the meaning of 'baud' ambiguous and the overall parameter semantics incomplete.

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 verb and resource: it 'Read[s] a serial port for N seconds' and 'judge[s] its log against a contract's expect/forbid patterns.' This distinguishes it from siblings like judge_serial (which likely only judges) by explicitly combining capture and judgment.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like judge_serial or capture_ws2812. 'Read AND judge' implies a combined use case, but no clear prerequisites, exclusions, or alternative references are given.

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

Deploy Server