Skip to main content
Glama
IBM

Physics MCP Server

by IBM

check_force_balance

Determines if a set of force vectors is balanced by computing net force and verifying equilibrium within a tolerance, essential for statics analysis.

Instructions

Check if forces are in equilibrium: ΣF = 0.

Verifies whether a system of forces is balanced (net force = 0).
Essential for statics problems and structural analysis.

Args:
    forces: List of force vectors [[x,y,z], ...] in Newtons (or JSON string)
    tolerance: Tolerance for equilibrium check (fraction, default 0.01)

Returns:
    Dict containing:
        - net_force: Net force vector [x, y, z] in Newtons
        - net_force_magnitude: Net force magnitude in Newtons
        - is_balanced: Whether forces are in equilibrium
        - individual_magnitudes: Magnitude of each force

Example - Bridge support forces:
    result = await check_force_balance(
        forces=[[0, 1000, 0], [0, 500, 0], [0, -1500, 0]],
        tolerance=0.01
    )
    # is_balanced = True if net force ≈ 0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forcesYes
toleranceNo
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It confirms a read-only equilibrium check but does not explicitly state that no state is modified, nor does it discuss error handling or limitations.

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 well-structured with a clear heading, explanation, args, returns, and an example. It is somewhat lengthy but each sentence adds value. Could be slightly tighter.

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?

The description explains the tool's purpose, inputs, and outputs in detail, including an example. However, it does not mention integration with simulations or error behavior, and no output schema is provided.

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 coverage is 0%, so the description fully compensates by explaining that 'forces' is a list of vectors or JSON string in Newtons and 'tolerance' is a fraction with default 0.01. This adds essential meaning beyond the schema's bare types.

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 'Check if forces are in equilibrium: ΣF = 0' and provides a specific verb-resource pair. It distinguishes from siblings like check_torque_balance by focusing solely on force equilibrium, and the example reinforces its purpose.

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 says 'Essential for statics problems and structural analysis,' giving context, but does not explicitly state when not to use this tool or compare it to alternatives like check_equilibrium or check_torque_balance.

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