Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_momentum

Calculate momentum vector from mass and velocity components. Use for analyzing collisions, recoil, and rocket propulsion.

Instructions

Calculate momentum from mass and velocity (p = mv).

Computes the momentum vector, which represents "quantity of motion."
Momentum is conserved in collisions, making it crucial for analyzing
impacts, explosions, and rocket propulsion.

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:
    MomentumResponse containing:
        - momentum: Momentum vector [x, y, z] in kg⋅m/s
        - magnitude: Momentum magnitude in kg⋅m/s

Tips for LLMs:
    - Momentum is a vector (has direction), unlike kinetic energy
    - Total momentum before collision = total momentum after (conservation)
    - Large mass × small velocity can equal small mass × large velocity
    - Use to analyze: collisions, recoil, rocket thrust

Example:
    # Momentum of a 70kg person running at 5 m/s
    result = await calculate_momentum(
        mass=70.0,
        velocity_x=5.0,
        velocity_y=0.0,
        velocity_z=0.0
    )
    print(f"Momentum: {result.magnitude:.1f} kg⋅m/s")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
velocity_xYes
velocity_yYes
velocity_zYes
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 describes the computation, the vector nature, and conservation, but does not explicitly state that it is a stateless, non-destructive operation. This is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with Args, Returns, Tips, and Example sections. It is front-loaded with the formula, every sentence adds value, and there is no redundancy.

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

Completeness4/5

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

The description explains the return structure (momentum vector and magnitude) and provides physics context. Minor omissions include no error handling guidance (e.g., negative mass) and implicit units for momentum (shown in example but not explicitly in description).

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?

The input schema has 0% description coverage. The description compensates excellently by explaining each parameter (mass must be positive, velocity components in m/s) and providing an example. This adds significant meaning beyond the bare schema.

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 explicitly states 'Calculate momentum from mass and velocity (p = mv)', clearly specifying the verb, resource, and formula. It distinguishes itself from sibling tools like calculate_force or calculate_kinetic_energy by directly naming momentum.

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 context on when to use the tool (e.g., analyzing impacts, explosions, rocket propulsion) and mentions conservation of momentum. However, it does not explicitly state when not to use it or compare it to alternative tools for collisions among the siblings.

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