Skip to main content
Glama

FFT bin location

bpj_bench_fft_bin_grid
Read-onlyIdempotent

Find the nearest one-sided FFT bin to a frequency for a real input block at the given sample rate.

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": {
      "sampleRate": "<sampleRate>",
      "size": "<size>",
      "target": "<target>"
    },
    "name": "bpj_bench_fft_bin_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
targetYes
sampleRateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds genuine domain context by specifying 'one-sided' and 'real input block', which constrains the result semantics. It does not disclose rounding/tie-breaking behavior for the nearest bin or what happens when the target exceeds Nyquist, which are the real behavioral questions here.

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 or redundancy. It is efficient, though the terseness leaves no room for the caveats the tool actually needs.

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?

There is no output schema, so the description is the only place an agent can learn what comes back — bin index, bin-center frequency, or magnitude — and it says nothing. For a numeric calculation tool with three undocumented parameters, the definition should also mention bin width and out-of-range target handling.

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 the parameter burden. It clarifies 'target' (a frequency) and 'sampleRate' implicitly, but never explains 'size' as the FFT length or its effect on bin spacing (sampleRate/size) and the number of one-sided bins. Only two of three parameters get meaningful treatment.

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 and resource: find the nearest one-sided FFT bin to a target frequency for a real input block at a given sample rate. That is materially more precise than the title alone and tells an agent what computation is performed. It does not, however, distinguish itself from nearby bench calculators such as bpj_bench_sample_alias, which an agent might plausibly confuse it with.

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 or when-not-to-use guidance, no named alternative, and no stated precondition such as the target needing to fall below Nyquist. The agent is left to infer the calling context entirely from the one-sentence 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.