Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_kinetic_energy

Calculate kinetic energy from mass and velocity components using KE = ½mv² for collision analysis, vehicle safety, and energy transfer calculations.

Instructions

Calculate kinetic energy from mass and velocity (KE = ½mv²).

Computes the energy of motion for a moving object. Energy is scalar
(direction doesn't matter, only speed). Useful for collision analysis,
vehicle safety, and understanding energy transfer.

Args:
    mass: Mass in kilograms (must be positive)
    velocity_x: X component of velocity in m/s
    velocity_y: Y component of velocity in m/s
    velocity_z: Z component of velocity in m/s

Returns:
    KineticEnergyResponse containing:
        - kinetic_energy: Energy in Joules (J)
        - speed: Velocity magnitude in m/s

Tips for LLMs:
    - 1 Joule = 1 kg⋅m²/s² = energy to lift 102g by 1m on Earth
    - Kinetic energy doubles mass → doubles energy, doubles speed → 4× energy
    - Car at highway speed (~30 m/s, 1500 kg) ≈ 675,000 J
    - Use to compare impact severity or stopping distances

Example:
    # Energy of a 0.145kg baseball at 40 m/s
    result = await calculate_kinetic_energy(
        mass=0.145,
        velocity_x=40.0,
        velocity_y=0.0,
        velocity_z=0.0
    )
    print(f"Kinetic energy: {result.kinetic_energy:.1f} J")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
velocity_xYes
velocity_yYes
velocity_zYes
Behavior5/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 and does so comprehensively. It explains the scalar nature of energy, provides practical examples, includes unit conversions, scaling relationships, and real-world context about car energy calculations. This gives the agent rich behavioral understanding beyond just the calculation.

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 (formula, explanation, args, returns, tips, example) and every sentence adds value. While comprehensive, it might be slightly verbose for a simple calculation tool, but the information density is high and well-organized.

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 provides exceptional completeness. It covers the formula, parameter meanings, return values, practical applications, scaling relationships, unit context, and a full working example - everything an agent needs to use this tool correctly.

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 documentation. It explains each parameter's meaning (mass in kg, velocity components in m/s), includes constraints (mass must be positive), and provides a complete working example showing how to use all four parameters correctly.

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 kinetic energy from mass and velocity using the formula KE = ½mv², with specific examples of applications like collision analysis and vehicle safety. It distinguishes itself from sibling tools like calculate_rotational_kinetic_energy by focusing on linear kinetic energy.

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 about when to use this tool (for computing energy of motion, collision analysis, vehicle safety, energy transfer) and includes helpful tips for LLMs. However, it doesn't explicitly state when not to use it or mention specific alternatives among the many sibling physics 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