Skip to main content
Glama

Clock drift budget

bpj_bench_clock_drift
Read-onlyIdempotent

Estimate accumulated timing error magnitude from an oscillator’s frequency tolerance and elapsed days.

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": {
      "ppm": "<ppm>",
      "days": "<days>"
    },
    "name": "bpj_bench_clock_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
ppmYes
daysYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and purity profile is fully covered by structured data. The description contributes the actual computational premise (error accumulated from ppm tolerance over elapsed days), which is useful, but it omits the drift model assumed (linear worst-case vs. statistical), the output unit (seconds, milliseconds), and whether the result is an absolute magnitude bound or an estimate with uncertainty.

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 the verb first and the two driving inputs trailing; no filler, no restatement of the title. It is perhaps slightly too terse for the gaps it leaves, but nothing in it is wasted.

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 no output schema and no annotations covering return values, the description is the only place an agent could learn what number comes back and in what unit — and it does not say. For a numeric estimator this omission means the agent cannot reliably interpret or present the result, so the definition is under-complete relative to the tool's job.

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 parameter meaning; it does map directly onto both parameters ('frequency tolerance' and 'elapsed days'). However, it adds no semantics beyond the schema's own titles and bounds — nothing about how ppm is interpreted (e.g. ±ppm worst case) or how fractional days under 1e-9 are handled.

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 ('Estimate') and a specific resource ('accumulated timing error magnitude'), plus the two inputs that drive it, so an agent can tell this is a drift-budget calculator rather than a generic clock tool. It does not explicitly differentiate itself from the near-named sibling bpj_subtitle_clock_drift or the other budget tools, leaving that inference to the reader.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implicit guidance comes from the phrase 'oscillator's frequency tolerance and elapsed days', which hints at a hardware-timing scenario but never says when that scenario applies or when a sibling (e.g. subtitle clock drift) is the better choice.

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.