Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_damped_oscillation

Calculate position and velocity of damped oscillators with friction or resistance. Determine damping regimes (underdamped, critically damped, overdamped) for systems like car suspensions or mechanical oscillators.

Instructions

Calculate damped oscillation with friction/resistance.

Real oscillators lose energy over time due to damping (air resistance,
friction). Three regimes: underdamped, critically damped, overdamped.

Args:
    mass: Mass in kg
    spring_constant: k in N/m
    damping_coefficient: b in kg/s (damping strength)
    time: Time t in seconds
    initial_position: Initial position in meters (default 1.0)
    initial_velocity: Initial velocity in m/s (default 0.0)

Returns:
    Dict containing:
        - position: x(t) in meters
        - velocity: v(t) in m/s
        - damping_ratio: ζ (zeta) = b/(2√(mk))
        - regime: "underdamped", "critically_damped", or "overdamped"

Damping regimes:
    - ζ < 1: Underdamped (oscillates, gradually decays)
    - ζ = 1: Critically damped (returns fastest without oscillating)
    - ζ > 1: Overdamped (slow return, no oscillation)

Example - Car suspension:
    result = await calculate_damped_oscillation(
        mass=300,  # kg (quarter car mass)
        spring_constant=20000,  # N/m
        damping_coefficient=2000,  # kg/s
        time=1.0
    )
    # Should be slightly underdamped for comfort

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
spring_constantYes
damping_coefficientYes
timeYes
initial_positionNo
initial_velocityNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains the tool's behavior by detailing the three damping regimes with their characteristics (oscillation patterns, return speed), the mathematical basis (damping ratio formula), and the return structure. It does not cover aspects like error handling or computational limits, but provides substantial context beyond basic functionality.

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 clear sections (purpose, args, returns, damping regimes, example) and uses bullet points for readability. It is appropriately sized for the tool's complexity, though the example paragraph is slightly verbose. Most sentences earn their place by adding necessary context or clarification.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is highly complete. It covers purpose, parameters with semantics, return values in detail (including the damping ratio and regime), behavioral context (damping regimes with explanations), and a practical example. This provides all necessary information for an agent to understand and use the tool effectively.

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?

Given 0% schema description coverage, the description fully compensates by providing detailed semantic information for all 6 parameters: physical meanings (e.g., 'Mass in kg', 'k in N/m'), units, default values for optional parameters, and their role in the calculation. This adds significant value beyond the bare schema, making parameter usage clear and complete.

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 the tool's purpose with a specific verb ('calculate') and resource ('damped oscillation'), distinguishing it from siblings like 'calculate_simple_harmonic_motion' or 'calculate_spring_mass_period' by explicitly mentioning friction/resistance and damping regimes. It provides a concise definition of damped oscillation in the first sentence.

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 clear context for when to use this tool by explaining that it models real oscillators with energy loss due to damping, and includes a practical example (car suspension) that illustrates a typical application scenario. However, it does not explicitly state when not to use it or name specific alternatives among the sibling tools.

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/IBM/chuk-mcp-physics'

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