Skip to main content
Glama

fourier_transform_expression

Transform a space or time-domain expression into its frequency-domain form. Useful for spectral analysis, signal processing, and periodic dosing evaluation.

Instructions

    Fourier transform: f(x) → F(k).

    ═══════════════════════════════════════════════════════════════════════
    🆕 PHASE 2 - NOT IN SYMPY-MCP OR NSFORGE v0.2.3!
    ═══════════════════════════════════════════════════════════════════════

    Transforms spatial/time function to frequency domain.

    USE CASES:
    - Periodic dosing analysis (repeated administration)
    - Spectral analysis (frequency components)
    - Signal processing (filter design)
    - Diffusion problems (spatial frequency)

    Args:
        expression: Space/time-domain expression f(x)
        space_var: Space/time variable (default: "x")
        freq_var: Frequency variable (default: "k")

    Returns:
        Fourier transform F(k)

    Examples:
        # Gaussian pulse
        fourier_transform_expression("exp(-x**2)", "x", "k")
        → {"result": "sqrt(pi)*exp(-pi**2*k**2)", ...}

        # Exponential decay
        fourier_transform_expression("exp(-abs(x))", "x", "k")
        → {"result": "2/(1 + k**2)", ...}

        # Rectangular pulse
        fourier_transform_expression("Heaviside(x+1) - Heaviside(x-1)", "x", "k")
        → {"result": "2*sin(k)/k", ...}

        # PK: Periodic dosing spectrum
        # Analyze frequency components of repeated doses
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freq_varNok
space_varNox
expressionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It communicates the transform direction, return format via examples (e.g., 'sqrt(pi)*exp(-pi**2*k**2)'), and parameter defaults. However, it does not disclose potential edge cases like unsupported inputs or unevaluated results, which would be valuable additional context.

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 well-structured with sections for args, returns, and examples, but includes some non-essential content such as the 'PHASE 2' banner and a lengthy list of use cases. It is efficient overall, though not as lean as a two-sentence description.

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

Completeness5/5

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

The description is complete for a transform tool, providing enough context through examples, use cases, and parameter docs. Even though an output schema exists, the examples clarify the exact return format, and the tool's behavior is fully specified for typical use cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by listing each argument (expression, space_var, freq_var) with its meaning and defaults. This goes beyond the schema's minimal type/title information, making parameter semantics completely clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Fourier transform: f(x) → F(k)' and 'Transforms spatial/time function to frequency domain,' using a specific verb and resource. This distinguishes it from sibling tools like inverse_fourier_transform_expression and laplace_transform_expression.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit use cases (periodic dosing, spectral analysis, signal processing, diffusion problems) and an example for PK analysis, giving clear context for when to apply the tool. It does not explicitly mention alternatives or exclusions, so it stops short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/u9401066/nsforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server