Skip to main content
Glama

Stereo mid-side sample encoder

bpj_bench_stereo_mid_side
Read-onlyIdempotent

Encode one normalized left/right stereo sample into reversible half-sum mid and half-difference side components.

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": {
      "left": "<left>",
      "right": "<right>"
    },
    "name": "bpj_bench_stereo_mid_side"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. Beyond that, the description adds meaningful behavioral context by specifying that the transform is reversible and by naming the exact mid/side components, though it does not describe output structure or edge-case handling.

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?

The definition is a single tightly written sentence with the core operation and output description front-loaded. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter mathematical transform with no output schema, the description is nearly complete: it identifies the inputs, the transform, and the resulting mid/side components. It could be slightly more explicit about the return shape, but the essential behavior is covered.

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 clarify that the two parameters are the left and right channels of one normalized stereo sample, but it adds little beyond the schema's own titles and min/max bounds, and does not explain numerical interpretation or error behavior for out-of-range values.

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 ('Encode') and resource ('one normalized left/right stereo sample') and even names the output components ('half-sum mid and half-difference side'). It is clear what the tool does, but it does not explicitly distinguish itself from any sibling tool, which keeps it below a 5.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no alternatives. Usage is only inferable from the purpose statement, so an agent is not told when this encoder is preferable to any other bench tool.

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.