Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_potential_energy

Calculate gravitational potential energy using mass, height, and gravity. Also determines the equivalent 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?

No annotations are provided, so the description bears full responsibility for transparency. It clearly states the formula, default gravity value, and that an additional derived value (equivalent kinetic velocity) is returned. It does not mention side effects or destruction, but as a calculation tool, that is appropriate.

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 moderately long but well-structured with sections (description, args, returns, example). It front-loads the core formula and then details parameters and output. A minor improvement could be trimming the example explanation, but overall it is clear and efficient.

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 output schema, the description fully describes the return values (potential_energy in Joules, equivalent_kinetic_velocity in m/s). With only 3 parameters, all documented, and no constraints or enums, the description covers all necessary context for correct invocation.

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%, yet the description fully explains each parameter: mass (kg), height (m), gravity (default 9.81 m/s²). It provides units, defaults, and an example that illustrates usage. The schema only provides types and defaults without descriptions, so the description adds essential meaning.

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 it calculates gravitational potential energy using the formula PE = mgh, and explicitly distinguishes from siblings by specifying the formula and that it also returns equivalent kinetic velocity. The verb 'calculate' and resource 'potential energy' are specific, and the addition of 'gravitational' reinforces the scope.

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 does not provide explicit guidance on when to use this tool versus alternatives like calculate_kinetic_energy or other potential energy forms. The example and formula imply its use case, but no 'when not to use' or comparative statements are given. Given many siblings, this is a gap.

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