Skip to main content
Glama
IBM

Physics MCP Server

by IBM

analyze_circular_orbit

Calculate orbital radius, velocity, period, and centripetal acceleration for a circular orbit at a specified altitude above a planet.

Instructions

Analyze circular orbit at given altitude above planet surface.

Comprehensive orbital analysis combining period, velocity, and acceleration.

Args:
    altitude: Altitude above surface in meters
    planet_mass: Planet mass in kg
    planet_radius: Planet radius in meters
    gravitational_constant: G in m³/(kg⋅s²) (default 6.674e-11)

Returns:
    Dict containing:
        - orbital_radius: r from planet center in meters
        - orbital_velocity: v in m/s
        - period_seconds: Orbital period in seconds
        - period_minutes: Orbital period in minutes
        - centripetal_acceleration: a_c in m/s²

Example - LEO satellite at 400km altitude:
    result = await analyze_circular_orbit(
        altitude=400000,  # 400 km
        planet_mass=5.972e24,  # Earth
        planet_radius=6.371e6  # Earth
    )
    # v ≈ 7,670 m/s, T ≈ 92.6 min

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altitudeYes
planet_massYes
planet_radiusYes
gravitational_constantNo

Implementation Reference

  • Core calculation function for analyzing circular orbit. Takes CircularOrbitRequest, computes orbital radius (r = R + h), orbital velocity (v = sqrt(GM/r)), orbital period (T = 2π sqrt(r³/GM)), period in minutes, and centripetal acceleration (a_c = v²/r). Returns CircularOrbitResponse.
    def analyze_circular_orbit(request: CircularOrbitRequest) -> CircularOrbitResponse:
        """Analyze a circular orbit at given altitude.
    
        Combines multiple orbital calculations into a comprehensive analysis.
    
        Args:
            request: Circular orbit request
    
        Returns:
            Complete orbital analysis
        """
        h = request.altitude
        R = request.planet_radius
        M = request.planet_mass
        G = request.gravitational_constant
    
        # Orbital radius (from planet center)
        r = R + h
    
        # Orbital velocity: v = √(GM/r)
        v = math.sqrt((G * M) / r)
    
        # Period: T = 2π√(r³/GM)
        T = 2.0 * math.pi * math.sqrt((r * r * r) / (G * M))
        T_min = T / 60.0
    
        # Centripetal acceleration
        a_c = (v * v) / r
    
        return CircularOrbitResponse(
            orbital_radius=r,
            orbital_velocity=v,
            period_seconds=T,
            period_minutes=T_min,
            centripetal_acceleration=a_c,
        )
  • MCP @tool decorated async wrapper for analyze_circular_orbit. Accepts altitude, planet_mass, planet_radius, gravitational_constant as parameters. Delegates to the core calculation function in circular_motion.py and returns model_dump dict.
    @tool  # type: ignore[arg-type]
    async def analyze_circular_orbit(
        altitude: float,
        planet_mass: float,
        planet_radius: float,
        gravitational_constant: float = 6.674e-11,
    ) -> dict:
        """Analyze circular orbit at given altitude above planet surface.
    
        Comprehensive orbital analysis combining period, velocity, and acceleration.
    
        Args:
            altitude: Altitude above surface in meters
            planet_mass: Planet mass in kg
            planet_radius: Planet radius in meters
            gravitational_constant: G in m³/(kg⋅s²) (default 6.674e-11)
    
        Returns:
            Dict containing:
                - orbital_radius: r from planet center in meters
                - orbital_velocity: v in m/s
                - period_seconds: Orbital period in seconds
                - period_minutes: Orbital period in minutes
                - centripetal_acceleration: a_c in m/s²
    
        Example - LEO satellite at 400km altitude:
            result = await analyze_circular_orbit(
                altitude=400000,  # 400 km
                planet_mass=5.972e24,  # Earth
                planet_radius=6.371e6  # Earth
            )
            # v ≈ 7,670 m/s, T ≈ 92.6 min
        """
        from ..circular_motion import CircularOrbitRequest, analyze_circular_orbit as analyze_orbit
    
        request = CircularOrbitRequest(
            altitude=altitude,
            planet_mass=planet_mass,
            planet_radius=planet_radius,
            gravitational_constant=gravitational_constant,
        )
        response = analyze_orbit(request)
        return response.model_dump()
  • CircularOrbitRequest Pydantic model with fields: altitude (meters, >= 0), planet_mass (kg, > 0), planet_radius (meters, > 0), gravitational_constant (default 6.674e-11).
    class CircularOrbitRequest(BaseModel):
        """Request for circular orbit analysis."""
    
        altitude: float = Field(..., description="Altitude above surface in meters", ge=0.0)
        planet_mass: float = Field(..., description="Planet mass in kg", gt=0.0)
        planet_radius: float = Field(..., description="Planet radius in meters", gt=0.0)
        gravitational_constant: float = Field(
            default=6.674e-11, description="Gravitational constant G in m³/(kg⋅s²)"
        )
  • CircularOrbitResponse Pydantic model with fields: orbital_radius (meters), orbital_velocity (m/s), period_seconds, period_minutes, centripetal_acceleration (m/s²).
    class CircularOrbitResponse(BaseModel):
        """Response for circular orbit analysis."""
    
        orbital_radius: float = Field(..., description="Orbital radius (from planet center) in meters")
        orbital_velocity: float = Field(..., description="Orbital velocity in m/s")
        period_seconds: float = Field(..., description="Orbital period in seconds")
        period_minutes: float = Field(..., description="Orbital period in minutes")
        centripetal_acceleration: float = Field(
            ..., description="Centripetal acceleration at this orbit in m/s²"
        )
Behavior4/5

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

With no annotations, the description effectively discloses the output structure (dict with orbital radius, velocity, period, acceleration) and the default gravitational constant. It lacks mention of error handling or constraints (e.g., altitude must be positive), but it is largely transparent for a physics computation tool.

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 distinct sections for purpose, arguments, returns, and example. Every sentence adds value and there is no redundancy. It is concise yet informative.

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 the absence of an output schema, the description fully enumerates return keys. It includes a helpful example. However, it could be more complete by mentioning assumptions (e.g., circular orbit, no atmospheric drag) and ensuring consistency in units. Still, it is largely adequate.

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 fully compensates by defining each parameter with units and providing a concrete example. This adds significant meaning beyond the minimal 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 analyzes a circular orbit at a given altitude, combining period, velocity, and acceleration. This distinguishes it from sibling tools like calculate_orbital_period or calculate_centripetal_force which compute single quantities.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., using individual calculation tools). The example hints at a typical use case but does not state when this combined analysis is preferred or not.

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