Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_escape_velocity

Calculate the minimum speed required for an object to escape a celestial body's gravitational pull using mass, radius, and gravitational constant inputs.

Instructions

Calculate escape velocity: v_escape = √(2GM/r).

Minimum speed needed to escape a celestial body's gravitational pull.
Independent of the escaping object's mass.

Args:
    mass: Mass of celestial body in kg
    radius: Radius of celestial body in meters
    gravitational_constant: G in m³/(kg⋅s²) (default 6.674e-11)

Returns:
    Dict containing:
        - escape_velocity: v_escape in m/s
        - escape_velocity_kmh: v_escape in km/h (for convenience)

Tips for LLMs:
    - Earth: v_escape ≈ 11,200 m/s (40,320 km/h)
    - Moon: v_escape ≈ 2,380 m/s
    - Sun: v_escape ≈ 617,500 m/s
    - Independent of escape direction or mass of escaping object

Example - Earth escape velocity:
    result = await calculate_escape_velocity(
        mass=5.972e24,  # Earth mass (kg)
        radius=6.371e6  # Earth radius (meters)
    )
    # v_escape ≈ 11,186 m/s

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
radiusYes
gravitational_constantNo
Behavior4/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 does an excellent job explaining key behavioral traits: it specifies the calculation is independent of the escaping object's mass and direction, provides the default gravitational constant value, and includes practical examples with real-world values. The only minor gap is not explicitly stating this is a pure calculation with no side effects.

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 front-loaded: starts with formula, then purpose, key property, parameters, returns, tips, and example. Every sentence earns its place - the tips provide valuable context without redundancy, and the example demonstrates proper usage efficiently.

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 pure calculation tool with no output schema, this description is exceptionally complete. It explains the formula, parameters, return values (including both m/s and km/h), provides real-world examples, and clarifies important physical properties. No annotations are needed for this straightforward mathematical operation.

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 explanations: mass in kg, radius in meters, gravitational constant with units m³/(kg⋅s²) and default value. It even includes an example with Earth's mass and radius values, giving complete semantic understanding 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 specific verb 'calculate' and resource 'escape velocity', providing the exact formula v_escape = √(2GM/r). It distinguishes this tool from siblings by focusing on gravitational escape velocity rather than other physics calculations like orbital period or centripetal force.

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 ('minimum speed needed to escape a celestial body's gravitational pull') and includes helpful examples for Earth, Moon, and Sun. However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the many sibling 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