Skip to main content
Glama
Sign In
REW MCP Server

REW MCP Server

by manuaero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rew_encode_array

Read-only

Encodes numeric sample arrays for REW frequency and impulse data imports, preparing values in the payload format required by Room EQ Wizard.

Instructions

Encode numeric samples for REW frequency/impulse data imports.

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": {
      "values": "<values>"
    },
    "name": "rew_encode_array"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish read-only, non-destructive, closed-world behavior, and the description is consistent with them while adding the intended import context. It discloses little about the transformation itself, such as the encoded representation, validation, or failure behavior.

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 single sentence is compact, front-loaded, and free of filler. Its missing technical detail is an completeness issue rather than a structural one and is scored in the other dimensions.

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?

The schema makes the basic call shape apparent, but the lack of an output schema and parameter documentation leaves the description with more burden than it meets. Without the sample layout or encoded output representation, an agent cannot confidently prepare data for an import or interpret the result.

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?

With 0% schema description coverage, "numeric samples" adds only minimal meaning to the required values array beyond its numeric type. The description does not explain sample ordering or layout, units, expected ranges, or how frequency and impulse samples should be represented.

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 gives a specific action and resource—"Encode numeric samples"—and identifies the REW frequency/impulse import domain. It does not explicitly distinguish the tool from siblings such as rew_decode_array or clarify the difference between preparing frequency and impulse data.

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 phrase "for REW frequency/impulse data imports" supplies an implied use case. There are no explicit prerequisites, when-not conditions, or alternatives to help an agent choose this tool over a sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools