Skip to main content
Glama

inverse_laplace_transform_expression

Convert frequency-domain expressions F(s) back into time-domain functions f(t) using inverse Laplace transforms. Ideal for solving differential equations, transfer functions, and pharmacokinetic models.

Instructions

    Inverse Laplace transform: F(s) → f(t).

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

    Transforms s-domain (Laplace) back to time-domain.

    CRITICAL FOR:
    - Getting time response from transfer function
    - Multi-compartment PK model solutions
    - Impulse/step response analysis
    - Converting algebraic solutions back to ODE solutions

    Args:
        expression: Frequency-domain expression F(s)
        freq_var: Frequency variable (default: "s")
        time_var: Time variable (default: "t")

    Returns:
        Time-domain function f(t)

    Examples:
        # Simple pole
        inverse_laplace_transform_expression("1/(s + k)", "s", "t")
        → {"result": "exp(-k*t)*Heaviside(t)", ...}

        # Two-compartment model (after partial fractions)
        inverse_laplace_transform_expression("A/(s + λ1) + B/(s + λ2)", "s", "t")
        → {"result": "A*exp(-λ1*t) + B*exp(-λ2*t)", ...}

        # Step response
        inverse_laplace_transform_expression("1/(s*(s + k))", "s", "t")
        → {"result": "(1 - exp(-k*t))/k", ...}

        # PK: Bolus injection response
        inverse_laplace_transform_expression("dose/(V*(s + k))", "s", "t")
        → {"result": "dose*exp(-k*t)/V", ...}

        # WORKFLOW: Use with apart_expression!
        # 1. apart_expression("F(s)", "s") → partial fractions
        # 2. inverse_laplace_transform_expression(...) → f(t)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freq_varNos
time_varNot
expressionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full behavioral burden. It provides return format ('Time-domain function f(t)') and examples showing Heaviside(t) output, plus a multi-step workflow. It does not disclose potential failure modes or assumptions, but the transform behavior is well illustrated.

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 explicit sections and front-loaded with the core purpose. However, the 'PHASE 2' banner and emoji decorations add noise, and the 'CRITICAL FOR' list could be tightened. Still, every functional section (Args, Returns, Examples) earns its place.

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 covers purpose, practical use cases, parameters, return value, examples including PK modeling, and a cross-tool workflow with apart_expression. With an output schema present and this rich textual context, the tool is fully contextualized.

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 coverage is 0%, but the Args section describes each parameter: expression (frequency-domain function), freq_var (default 's'), time_var (default 't'). Examples also demonstrate positional usage, fully compensating for missing schema descriptions.

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 opens with 'Inverse Laplace transform: F(s) → f(t)' and 'Transforms s-domain (Laplace) back to time-domain,' clearly identifying the operation and resource. It distinguishes itself from the sibling laplace_transform_expression by explicitly naming the inverse direction.

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 'CRITICAL FOR' section lists concrete application contexts (time response, PK models, impulse/step response, converting algebraic solutions). It also includes a workflow reference to apart_expression. However, it does not explicitly state when not to use this tool or compare it with inverse_fourier_transform_expression.

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