Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_orbital_period

Calculate orbital period for circular orbits using Kepler's Third Law. Input orbital radius and central body mass to get period, velocity, and time conversions.

Instructions

Calculate orbital period: T = 2π√(r³/GM).

Kepler's Third Law for circular orbits. Period depends on orbital
radius and central body mass.

Args:
    orbital_radius: Orbital radius in meters (from center of central body)
    central_mass: Mass of central body in kg
    gravitational_constant: G in m³/(kg⋅s²) (default 6.674e-11)

Returns:
    Dict containing:
        - period: Orbital period in seconds
        - orbital_velocity: v in m/s
        - period_hours: Period in hours (for convenience)
        - period_days: Period in days (for convenience)

Tips for LLMs:
    - Higher orbit → longer period
    - More massive central body → shorter period
    - Earth: M = 5.972e24 kg, R = 6.371e6 m
    - Moon orbit: r ≈ 384,400 km, T ≈ 27.3 days
    - ISS orbit: r ≈ 6,771 km (altitude 400 km), T ≈ 90 minutes

Example - ISS orbit:
    result = await calculate_orbital_period(
        orbital_radius=6.771e6,  # meters
        central_mass=5.972e24  # Earth mass (kg)
    )
    # T ≈ 5,558 seconds ≈ 92.6 minutes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orbital_radiusYes
central_massYes
gravitational_constantNo
Behavior5/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 an excellent job. It explains the mathematical behavior (Kepler's Third Law), provides the exact formula, describes what gets calculated (period plus additional derived values), includes default values, and offers practical examples with real-world data.

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. It starts with the core purpose and formula, then explains parameters, returns, and provides practical tips and examples. Every section earns its place, with no redundant information and excellent front-loading of the most important information.

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 3-parameter calculation tool with no annotations and no output schema, the description provides exceptional completeness. It covers the mathematical basis, parameter meanings, return values (including multiple convenience conversions), practical examples, and even includes helpful tips about orbital relationships. Nothing essential is missing.

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: orbital radius 'in meters (from center of central body)', central mass 'in kg', gravitational constant 'G in m³/(kg⋅s²)' with default value. It adds meaningful context beyond what the bare schema provides.

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 orbital period using Kepler's Third Law for circular orbits, specifying the exact formula T = 2π√(r³/GM). It distinguishes from siblings like 'calculate_escape_velocity' or 'calculate_centripetal_force' by focusing specifically on period calculation rather than other orbital mechanics.

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 for when to use this tool (circular orbits, period calculation) and includes helpful examples (Earth, Moon, ISS). However, it doesn't explicitly state when NOT to use it or name specific alternative tools from the sibling list for different orbital calculations.

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