Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_potential_energy

Calculate gravitational potential energy using mass, height, and gravity, and determine the equivalent kinetic velocity if the object falls from that height.

Instructions

Calculate gravitational potential energy.

Computes PE = mgh (mass × gravity × height).
Also returns the equivalent velocity if the object falls from that height.

Args:
    mass: Object mass in kilograms
    height: Height above reference point in meters
    gravity: Gravitational acceleration in m/s² (default 9.81 for Earth)

Returns:
    Dict containing:
        - potential_energy: PE in Joules
        - equivalent_kinetic_velocity: Speed if dropped from height (m/s)

Example - Object at 10m height:
    result = await calculate_potential_energy(mass=2.0, height=10.0)
    # PE = 196.2 J
    # Velocity if dropped = 14.0 m/s

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
heightYes
gravityNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing the calculation formula, default gravity value, and return structure. It explains what gets computed (PE and equivalent velocity) and the default behavior. However, it doesn't mention error handling, numerical precision, or domain constraints.

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?

Perfectly structured and appropriately sized: purpose statement, formula, additional output, parameter details, return format, and concrete example. Every sentence earns its place with zero waste, and information is front-loaded effectively.

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?

Given no annotations and no output schema, the description provides excellent coverage of inputs, calculation logic, and return values. The example adds practical clarity. It's nearly complete for this standalone calculation tool, though could mention edge cases like negative values.

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?

Schema description coverage is 0%, so the description must compensate fully. It provides complete parameter semantics: mass (kilograms), height (meters), gravity (m/s² with Earth default). This adds essential meaning beyond the bare schema types, including units and default values.

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 specific verb ('calculate') and resource ('gravitational potential energy'), and distinguishes from siblings by focusing on PE=mgh calculation rather than other physics calculations like kinetic energy or force. The title is null, so the description fully defines the purpose.

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

Usage Guidelines3/5

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

The description implies usage through the formula explanation and example, but doesn't explicitly state when to use this tool versus alternatives like calculate_kinetic_energy or calculate_work_power. No explicit guidance on when-not-to-use or prerequisites is provided.

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