Skip to main content
Glama
IBM

Physics MCP Server

by IBM

check_torque_balance

Verifies if a system of torques is in equilibrium by computing net torque and comparing it to zero within a specified tolerance. Solves rotational equilibrium problems.

Instructions

Check if torques are in equilibrium: Στ = 0.

Verifies whether a system of torques is balanced (net torque = 0).
Essential for rotational equilibrium and lever problems.

Args:
    torques: List of torque vectors [[x,y,z], ...] in N⋅m (or JSON string)
    tolerance: Tolerance for equilibrium check (fraction, default 0.01)

Returns:
    Dict containing:
        - net_torque: Net torque vector [x, y, z] in N⋅m
        - net_torque_magnitude: Net torque magnitude in N⋅m
        - is_balanced: Whether torques are in equilibrium
        - individual_magnitudes: Magnitude of each torque

Example - Seesaw balance:
    result = await check_torque_balance(
        torques=[[0, 0, 100], [0, 0, -100]],
        tolerance=0.01
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torquesYes
toleranceNo

Implementation Reference

  • Async MCP tool handler that parses input, creates TorqueBalanceRequest, calls the core calculation, and returns the response dict.
    @tool  # type: ignore[arg-type]
    async def check_torque_balance(
        torques: list[list[float]] | str,
        tolerance: float = 0.01,
    ) -> dict:
        """Check if torques are in equilibrium: Στ = 0.
    
        Verifies whether a system of torques is balanced (net torque = 0).
        Essential for rotational equilibrium and lever problems.
    
        Args:
            torques: List of torque vectors [[x,y,z], ...] in N⋅m (or JSON string)
            tolerance: Tolerance for equilibrium check (fraction, default 0.01)
    
        Returns:
            Dict containing:
                - net_torque: Net torque vector [x, y, z] in N⋅m
                - net_torque_magnitude: Net torque magnitude in N⋅m
                - is_balanced: Whether torques are in equilibrium
                - individual_magnitudes: Magnitude of each torque
    
        Example - Seesaw balance:
            result = await check_torque_balance(
                torques=[[0, 0, 100], [0, 0, -100]],
                tolerance=0.01
            )
        """
        from ..statics import TorqueBalanceRequest
        from ..statics import check_torque_balance as check_torques
    
        if isinstance(torques, str):
            torques = json.loads(torques)
    
        request = TorqueBalanceRequest(torques=torques, tolerance=tolerance)
        response = check_torques(request)
        return response.model_dump()
  • Pydantic model for torque balance input (torques, tolerance).
    class TorqueBalanceRequest(BaseModel):
        """Request for torque balance verification."""
    
        torques: list[list[float]] = Field(..., description="List of torque vectors [x, y, z] in N⋅m")
        tolerance: float = Field(
            default=0.01, description="Tolerance for equilibrium check (fraction)", ge=0.0
        )
    
    
    class TorqueBalanceResponse(BaseModel):
        """Response for torque balance verification."""
    
        net_torque: list[float] = Field(..., description="Net torque vector [x, y, z] in N⋅m")
        net_torque_magnitude: float = Field(..., description="Net torque magnitude in N⋅m")
        is_balanced: bool = Field(..., description="Whether torques are in equilibrium")
        individual_magnitudes: list[float] = Field(
            ..., description="Magnitude of each input torque in N⋅m"
        )
  • Pydantic model for torque balance output (net_torque, net_torque_magnitude, is_balanced, individual_magnitudes).
    class TorqueBalanceResponse(BaseModel):
        """Response for torque balance verification."""
    
        net_torque: list[float] = Field(..., description="Net torque vector [x, y, z] in N⋅m")
        net_torque_magnitude: float = Field(..., description="Net torque magnitude in N⋅m")
        is_balanced: bool = Field(..., description="Whether torques are in equilibrium")
        individual_magnitudes: list[float] = Field(
            ..., description="Magnitude of each input torque in N⋅m"
        )
  • Core calculation function that sums torque vectors, computes magnitudes, and determines if the system is balanced.
    def check_torque_balance(request: TorqueBalanceRequest) -> TorqueBalanceResponse:
        """Check if torques are in equilibrium: Στ = 0.
    
        Args:
            request: Torque balance request
    
        Returns:
            Torque balance analysis
        """
        net_torque = _vector_add(request.torques)
        net_magnitude = _vector_magnitude(net_torque)
    
        individual_magnitudes = [_vector_magnitude(t) for t in request.torques]
        total_magnitude = sum(individual_magnitudes)
    
        is_balanced = (
            net_magnitude <= request.tolerance * total_magnitude if total_magnitude > 0 else True
        )
    
        return TorqueBalanceResponse(
            net_torque=net_torque,
            net_torque_magnitude=net_magnitude,
            is_balanced=is_balanced,
            individual_magnitudes=individual_magnitudes,
        )
  • Importing the statics module registers all @tool-decorated functions (including check_torque_balance) via the chuk_mcp_server tool decorator.
    from .tools import (
        basic,
        rotational,
        oscillations,
        circular_motion,
        collisions,
        conservation,
        fluid as fluid_tools,
        kinematics_tools,
        statics,
        convert_units as unit_conversion_tools,
    )
    
    # Silence unused import warnings - these imports register @tool decorated functions
    _ = (
        basic,
        unit_conversion_tools,
        rotational,
        oscillations,
        circular_motion,
        collisions,
        conservation,
        fluid_tools,
        kinematics_tools,
        statics,
    )
Behavior4/5

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

Describes the tool's behavior (checking equilibrium, returning net torque and balance status) without annotations. While it doesn't explicitly state read-only or lack of side effects, the context implies a pure computation. Could be improved by noting it does not modify state.

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?

Well-structured with sections for Args, Returns, and Example, but the description is somewhat lengthy. Every sentence serves a purpose, but it could be slightly more concise while retaining clarity.

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?

With no annotations and no output schema, the description provides complete information: purpose, input parameters, return value structure, and a concrete example. No gaps are evident.

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?

Input schema has 0% description coverage, so the description fully explains the two parameters: torques (list of vectors or JSON string) and tolerance (fraction with default 0.01). This adds significant value beyond the 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?

Clearly states the tool checks torque equilibrium (Στ = 0), specifying the verb 'check' and the resource 'torques equilibrium'. Distinguishes from sibling tools like check_force_balance and check_equilibrium by focusing specifically on torques.

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?

Provides context for usage ('Essential for rotational equilibrium and lever problems') and an example (seesaw balance), but does not explicitly describe when not to use or mention alternative 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