Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_projectile_motion

Calculate projectile motion trajectory including maximum height, range, and flight time for ballistics, sports analysis, or educational demonstrations.

Instructions

Calculate projectile motion trajectory using kinematic equations.

Computes the complete trajectory of a projectile launched at an angle,
including maximum height, range, time of flight, and sample trajectory points.
Perfect for ballistics, sports analysis, or educational demonstrations.

Args:
    initial_velocity: Initial velocity in meters per second (m/s). Must be positive.
    angle_degrees: Launch angle in degrees from horizontal (0-90).
        0° = horizontal, 45° = maximum range, 90° = straight up
    initial_height: Initial height above ground in meters. Default 0.0 (ground level).
    gravity: Gravitational acceleration in m/s². Default 9.81 (Earth surface).
        Use 1.62 for Moon, 3.71 for Mars, etc.

Returns:
    ProjectileMotionResponse containing:
        - max_height: Maximum height reached (meters)
        - range: Horizontal distance traveled (meters)
        - time_of_flight: Total time in air (seconds)
        - trajectory_points: List of [x, y] sample points for plotting

Tips for LLMs:
    - 45° gives maximum range on flat ground (no air resistance)
    - For R3F visualization: convert trajectory_points to 3D by adding z=0
    - trajectory_points are evenly spaced in time (50 samples)
    - Air resistance is NOT modeled - this is ideal ballistic motion
    - Use for: cannon balls, baseballs, basketball shots, water fountains

Example:
    # Calculate trajectory of a cannonball fired at 50 m/s at 30°
    result = await calculate_projectile_motion(
        initial_velocity=50.0,
        angle_degrees=30.0,
        initial_height=2.0
    )
    print(f"Range: {result.range:.1f}m, Max height: {result.max_height:.1f}m")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initial_velocityYes
angle_degreesYes
initial_heightNo
gravityNo
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 and excels by disclosing key behavioral traits: it models ideal ballistic motion (no air resistance), uses evenly spaced time samples (50 points), and includes practical tips for visualization (e.g., converting to 3D). It also notes defaults and constraints, such as positive initial velocity and angle range implications.

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 (Args, Returns, Tips, Example) and front-loaded key information. It is appropriately sized but could be slightly more concise by integrating some tips into the main description. Every sentence adds value, though minor trimming is possible.

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?

Given no annotations, no output schema, and low schema coverage, the description provides comprehensive context: it explains the tool's purpose, usage, parameters, return values (including detailed response structure), limitations (no air resistance), and practical examples. This makes it complete and self-sufficient for an AI agent.

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 schema description coverage is 0%, so the description must compensate fully. It does so by explaining each parameter's meaning, units, constraints (e.g., initial_velocity must be positive), defaults (initial_height=0.0, gravity=9.81), and contextual examples (e.g., gravity values for Moon/Mars). This adds significant value 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 clearly states the tool calculates projectile motion trajectory using kinematic equations, specifying it computes maximum height, range, time of flight, and trajectory points. It distinguishes from sibling tools like 'calculate_projectile_with_drag' by emphasizing ideal ballistic motion without air resistance, making the purpose specific and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool (e.g., for ballistics, sports analysis, educational demonstrations) and when not to use it (air resistance is NOT modeled). It provides alternatives by mentioning 'calculate_projectile_with_drag' for cases with drag, offering clear guidance on tool selection.

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