Skip to main content
Glama

Display timing pixel clock

bpj_bench_display_refresh_budget
Read-onlyIdempotent

Compute required pixel clock and line frequency from total timing counts including blanking intervals.

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": {
      "hTotal": "<hTotal>",
      "vTotal": "<vTotal>",
      "refresh": "<refresh>"
    },
    "name": "bpj_bench_display_refresh_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
hTotalYes
vTotalYes
refreshYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered externally. The description adds one useful behavioral fact - that hTotal/vTotal must encompass blanking intervals - but says nothing about output units, precision, or rounding.

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 wasted words, leading with the computation and following with the input condition. It is lean but could trade a few extra words for a note on output units.

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?

For a three-parameter pure calculation with no output schema, the description covers the inputs' meaning but leaves the return values (pixel clock in Hz, line frequency in Hz) and their units implicit. Adequate to invoke correctly, but not fully self-contained.

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%, though the schema titles ('Total pixel clocks per line', 'Total lines per frame', 'Refresh rate (Hz)') carry basic meaning. The description compensates with the key insight that the totals include blanking, which materially affects how hTotal/vTotal should be supplied, but gives no unit or range detail beyond that.

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 states a specific verb (compute) and the exact outputs (pixel clock and line frequency), which distinguishes it from adjacent bench tools. It does not, however, explicitly differentiate itself from siblings like bpj_bench_clock_drift or bpj_design_display_pixel_pitch, so the agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The phrase 'from total timing counts including blanking intervals' hints at the appropriate input context but does not tell the agent when this tool is the right choice versus the many other budget/bench siblings.

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.