Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_normal_force

Calculate the normal force on an inclined plane given mass, angle, gravity, and optional additional perpendicular force. Returns normal force and weight components.

Instructions

Calculate normal force on an inclined plane.

On an incline at angle θ:
- N = mg cos(θ) + F_additional
- Weight component perpendicular: mg cos(θ)
- Weight component parallel: mg sin(θ)

Args:
    mass: Object mass in kg
    gravity: Gravitational acceleration in m/s² (default 9.81)
    angle_degrees: Incline angle in degrees (0 = horizontal)
    additional_force: Additional perpendicular force in Newtons (optional)

Returns:
    Dict containing:
        - normal_force: Normal force in Newtons
        - weight_component_perpendicular: Weight component ⊥ to surface
        - weight_component_parallel: Weight component ∥ to surface

Example - Box on 30° ramp:
    result = await calculate_normal_force(
        mass=10.0,
        angle_degrees=30.0
    )
    # normal_force ≈ 84.9 N

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massYes
gravityNo
angle_degreesNo
additional_forceNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it's a calculation tool (implied non-destructive), includes default values (gravity=9.81, angle_degrees=0), and describes the return format in detail. It doesn't mention error handling or computational limits, but covers the essential behavior well for this type of 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 and appropriately sized. It starts with the core purpose, provides necessary physics context, details parameters and returns, and includes a practical example. Every sentence earns its place without redundancy, and information is front-loaded effectively.

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?

Given the tool's moderate complexity (physics calculation with 4 parameters), no annotations, and no output schema, the description is complete. It covers purpose, usage context, parameter semantics, return values, and includes an example. This provides all needed information for an AI agent to correctly invoke the tool.

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 explaining all 4 parameters in the Args section: their meanings (e.g., 'Object mass in kg'), units, optionality, and defaults. It adds significant value beyond the bare schema, making parameter usage clear.

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's purpose: 'Calculate normal force on an inclined plane.' It specifies the verb ('calculate') and resource ('normal force'), and distinguishes it from sibling tools like 'calculate_force' or 'calculate_static_friction' by focusing on the specific physics scenario of an inclined plane.

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: for calculating normal force on an inclined plane, including the formula and components. However, it does not explicitly state when not to use it or mention alternatives among the many sibling physics calculation tools, which would be needed for a score of 5.

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