Skip to main content
Glama
Sign In
REW MCP Server

REW MCP Server

by manuaero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rew_get_measurement

Read-only

Retrieve a measurement summary or endpoint data by UUID, including frequency response, impulse response, group delay, distortion, or RT60, and decode paginated Base64 float32 samples.

Instructions

Get measurement summary or endpoint data such as frequency-response, impulse-response, group-delay, distortion or rt60. Use UUID. Decode Base64 float32 data with frequency/time coordinates and paginated samples.

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": {
      "measurement_id": "<measurement_id>"
    },
    "name": "rew_get_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
decodeNo
offsetNo
data_typeNo
max_pointsNo
measurement_idYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral detail: payloads are Base64 float32 with frequency/time coordinates and pagination. It stops short of stating return shape, size limits, or what the summary versus endpoint variants contain.

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?

Three short, front-loaded sentences with no filler; the data-type enumeration and decode note earn their place. The 'Use UUID' fragment is telegraphic and slightly out of place among fuller sentences.

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

Completeness3/5

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

No output schema, a nested 'query' object, and 0% schema coverage mean the description should explain more. It covers the data format and rough pagination but omits what the query object accepts, valid data_type values, and default behaviors, leaving an agent to guess on several parameters.

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% across six parameters, so the description must carry the load. It explains measurement_id (UUID), decode (Base64/float32), and pagination at a high level, but leaves 'query', 'data_type', 'max_points' defaults, and offset semantics undocumented.

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?

Specific verb 'Get' plus resource 'measurement summary or endpoint data', with an enumerated list of data types (frequency-response, impulse-response, group-delay, distortion, rt60). It implicitly separates itself from analysis/export siblings by emphasizing raw summary/endpoint retrieval, though it never names an alternative.

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?

'Use UUID' is a parameter hint, not usage guidance. The description never states when to pick this over rew_analyze_measurement, rew_export_measurement, or rew_list_measurements, nor any precondition for retrieval.

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