Skip to main content
Glama

Sampled tone alias

bpj_bench_sample_alias
Read-onlyIdempotent

Fold a sinusoidal input into the first Nyquist band for the indicated real-valued 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>",
      "frequency": "<frequency>"
    },
    "name": "bpj_bench_sample_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequencyYes
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 this is a read-only, idempotent, non-destructive, closed-world operation, so the description need not restate safety. The description adds domain behavior by saying it folds a sinusoid into the first Nyquist band, but it does not explain edge cases such as behavior at or below Nyquist, return format, or exact folding semantics.

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?

The description is a single efficient sentence with no filler and the operation is front-loaded. Its brevity is appropriate, though it leaves important behavioral details unstated.

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?

For a calculation tool with no output schema, the description should explain what the result is and how it should be interpreted. It states the transformation concept but does not describe the return value, parameter meanings in depth, or usage context, leaving the agent to infer too much.

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%, and the description does not compensate by defining the two parameters in detail. It implicitly references frequency ("sinusoidal input") and sample rate, but adds little beyond the schema's titles and numeric constraints, and does not clarify units or expected ranges.

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 uses a specific verb, "Fold," and names the resource/operation: sinusoidal input into the first Nyquist band at a given real-valued sample rate. It is clear enough to identify the calculation, but it does not distinguish this tool from nearby benchmark utilities or state the output explicitly.

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 conditions for choosing this tool over alternatives, and no exclusions or prerequisites. The phrase "indicated real-valued sample rate" gives context but does not guide tool selection.

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.