Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_simple_harmonic_motion

Calculate position, velocity, and acceleration for oscillating systems like springs and pendulums using the simple harmonic motion equation x(t) = A cos(ωt + φ).

Instructions

Calculate simple harmonic motion: x(t) = A cos(ωt + φ).

Position, velocity, and acceleration for sinusoidal oscillation.
Models ideal springs, pendulums, and many other oscillating systems.

Args:
    amplitude: Amplitude A in meters (maximum displacement)
    angular_frequency: ω in rad/s (ω = 2πf)
    time: Time t in seconds
    phase: Phase shift φ in radians (default 0)

Returns:
    Dict containing:
        - position: x(t) in meters
        - velocity: v(t) = -Aω sin(ωt + φ) in m/s
        - acceleration: a(t) = -Aω² cos(ωt + φ) in m/s²

Tips for LLMs:
    - Position and acceleration are 180° out of phase
    - Maximum velocity occurs at equilibrium (x = 0)
    - Maximum acceleration occurs at maximum displacement

Example - Oscillating mass:
    result = await calculate_simple_harmonic_motion(
        amplitude=0.1,  # 10cm amplitude
        angular_frequency=5.0,  # rad/s
        time=1.0  # at t = 1s
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amplitudeYes
angular_frequencyYes
timeYes
phaseNo
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 and does well by specifying the mathematical behavior (formulas for position, velocity, acceleration), return format (dictionary with specific keys), and practical tips about phase relationships and maxima. It doesn't cover error conditions or computational limitations.

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?

Well-structured with formula, context, parameter details, return format, and usage tips, but could be more front-loaded; the core purpose is clear early, though the 'Tips for LLMs' section adds value but extends length.

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 4-parameter tool with no annotations and no output schema, the description is complete: it explains what the tool does, when to use it, all parameter meanings, the return structure, and includes practical examples and tips for proper usage.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter semantics: physical meanings (amplitude as 'maximum displacement'), units (meters, rad/s, seconds, radians), mathematical relationships (ω = 2πf), and default values (phase defaults to 0).

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 calculates simple harmonic motion with the specific formula x(t) = A cos(ωt + φ), distinguishing it from sibling tools like calculate_damped_oscillation or calculate_spring_mass_period by focusing on ideal sinusoidal oscillation without damping or specific system parameters.

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 ('Models ideal springs, pendulums, and many other oscillating systems'), but doesn't explicitly state when NOT to use it or mention specific alternatives like calculate_damped_oscillation for non-ideal systems.

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