Skip to main content
Glama
Sign In
hwcontract

hwcontract

by MohibShaikh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

judge_serial

Judge captured serial logs against expect/forbid patterns, no hardware needed, to get pass/marginal/fail verdicts for iterating on contracts.

Instructions

Judge a captured serial log against expect/forbid patterns. No hardware; use for replay or logs another tool already captured.

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>",
      "log": "<log>"
    },
    "name": "judge_serial"
  }
}

Input Schema

NameRequiredDescriptionDefault
logYes
contract_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description discloses that the tool does not require hardware, which is a key behavioral trait. However, it does not explicitly state read-only behavior or side effects, leaving some ambiguity for the agent.

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 two sentences, front-loaded with the core action, and contains no unnecessary information.

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?

The tool is simple with two string parameters and no output schema. The description conveys the purpose and usage context but does not specify the return value or output format, which could leave an agent uncertain about how to interpret the results.

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?

The schema has no descriptions (0% coverage). The description mentions 'serial log' and 'expect/forbid patterns', which gives partial meaning to the `log` and `contract_path` parameters, but it doesn't explain their format or relationship clearly.

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: judging a captured serial log against expect/forbid patterns. It also distinguishes itself from hardware-related tools by noting 'No hardware', making it stand out among siblings like capture_ws2812 and check_serial.

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?

The description explicitly specifies when to use this tool: for replay or logs already captured, and states it is not for hardware. This gives clear guidance on when to invoke it, though it doesn't explicitly name alternative tools like check_serial for live use.

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