Skip to main content
Glama

Ideal unipolar ADC code

bpj_bench_adc_quantizer
Read-onlyIdempotent

Map a unipolar input into uniform ideal ADC bins, clipping the upper endpoint to the highest code.

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": {
      "bits": "<bits>",
      "ref": "<ref>",
      "input": "<input>"
    },
    "name": "bpj_bench_adc_quantizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
bitsYes
inputYes

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 covered. The description contributes genuine behavioral context by disclosing that the upper endpoint is clipped to the highest code, but it does not state the rounding rule (floor vs round) or the queryable code range, which materially affects results.

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?

A single front-loaded sentence with the core operation first and the edge-case caveat second; no redundant wording or filler.

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?

This is a pure numerical transform with no output schema and zero schema-description coverage, so the definition should state the return type and range (e.g., integer code in 0..2^bits-1) and the quantization convention. Neither is present, leaving an agent unable to predict the output of a three-required-parameter computation.

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 carry parameter meaning, and it largely does not: 'ref' (full-scale reference in volts), 'bits' (bit depth, 1-32) and 'input' are only gestured at via 'unipolar input' and 'bins'. Units, the meaning of 'ref', and how 'bits' determines bin count are left to the schema titles alone.

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?

States a specific operation (map a unipolar input into uniform ideal ADC bins) with a named domain concept that separates it from siblings like bpj_bench_dac_reconstruction or bpj_bench_sample_alias. It is clear what the tool does, though it does not explicitly name a sibling to defer to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'unipolar' implicitly scopes usage (non-negative inputs only) and the clipping note hints at end-of-range handling, but there is no explicit when-to-use or when-not-to-use guidance and no comparison to adjacent bench tools. Usage must be inferred.

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.