FASTMEAN MCP

Overview Schema Source Related Servers Discussions Admin

fastmean_spectrum

Compute amplitude, phase, and PSD spectra from FASTMEAN transient samples by interpolating onto a uniform grid and applying rFFT while retaining source CSV, window, and normalization.

Instructions

Return spectrum amplitude/phase/PSD of real FASTMEAN transient samples.

FASTMEAN calculates time samples. NumPy interpolates onto a uniform grid and performs rFFT; the PNG is Matplotlib, not a native FFT-window screenshot. Native source CSV, selected window and transform normalization are retained.

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": {
      "path": "<path>",
      "signal": "<signal>"
    },
    "name": "fastmean_spectrum"
  }
}

Input Schema

Name	Required	Default
`eps`	No
`path`	Yes
`step`	No
`stop`	No
`points`	No
`signal`	Yes
`window`	No
`timeout`	No
`overrides`	No
`definitions`	No
`window_function`	No	hann

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Oct 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so safety is mostly covered. The description adds useful context beyond them: the output PNG is Matplotlib-generated, a native source CSV is retained, and the chosen window/normalization are preserved -- implying file artifacts are written. It still omits side effects like where files land and whether prior outputs are overwritten.

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?

Four short sentences, front-loaded with the return value, with no filler. The 'PNG is Matplotlib, not a native FFT-window screenshot' caveat earns its place by preventing a misread of the output, though it is slightly oddly framed.

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?

With no output schema, 11 undocumented parameters, and 0% schema coverage, the description should explain the sampling/FFT parameters and the return shape. It names the return quantities but leaves the entire input contract and file output location unexplained, which is insufficient for a tool this configurable.

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% across 11 parameters, so the description must compensate and largely does not. Only 'window' and normalization are touched on loosely; path, signal, eps, step, stop, points, timeout, overrides, definitions and window_function get no meaning from the description, leaving the agent to guess at time-domain sampling vs frequency resolution.

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?

States a specific verb and resource: return amplitude/phase/PSD spectrum of real FASTMEAN transient samples. The note that NumPy/rFFT does the transform while FASTMEAN only produces time samples cleanly separates it from fastmean_transient. It does not explicitly contrast with fastmean_harmonics or fastmean_plot, but the resource is unambiguous.

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 statement of when to use this tool versus alternatives such as fastmean_harmonics or fastmean_plot, and no prerequisites (e.g., must a transient run exist first, or does path point to a result file?). The agent must infer the workflow entirely.

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