Skip to main content
Glama

UART frame time

bpj_bench_uart_wire_time
Read-onlyIdempotent

Estimate UART wire time including one start bit, selected data width, parity, and stop bits per frame.

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": {
      "baud": "<baud>",
      "data": "<data>",
      "parity": "<parity>",
      "stop": "<stop>",
      "frames": "<frames>"
    },
    "name": "bpj_bench_uart_wire_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
baudYes
dataYes
stopYes
framesYes
parityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world computation, so the safety profile is covered. The description adds real model detail by fixing one start bit and stating that parity and stop bits are counted per frame, but it omits the output units (seconds, bit periods, or µs) and whether idle/gap time between frames is included.

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?

A single front-loaded sentence with no filler; the computational assumptions are stated compactly. It is efficient, though it spends its one sentence on inclusion details rather than on the missing units and usage context.

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?

With five required parameters, 0% schema coverage, and no output schema, the description is the only source of return-value meaning, yet it never states the result's units or whether the returned value is scaled by 'frames'. For a pure calculation tool that is a significant omission an agent cannot recover from elsewhere.

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 0%, so the description must carry the parameter meaning, and it does partially: it maps 'data width', 'parity', 'stop bits' to the corresponding bit-count fields and implies frames are counted. It never mentions 'baud' explicitly, and the parity field (integer 0-1) remains ambiguous between a parity-bit count and a parity mode, leaving a real gap for a low-coverage schema.

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 names a specific verb and resource ('Estimate UART wire time') and enumerates the frame components included (start bit, data width, parity, stop bits), which is clearly distinguishable from framing siblings like bpj_slip_frame or bpj_cobs_frame. It stops short of explicitly differentiating itself from those siblings, so it lands at a clear-but-not-routed 4.

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?

There is no when-to-use guidance, no statement of the model's assumptions (e.g., asynchronous framing, no inter-frame idle), and no pointer to alternatives such as the other frame-timing tools. The agent must infer the applicability entirely from the tool name and the one-line purpose.

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.