Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_bernoulli

Calculate pressure differences in flowing fluids using Bernoulli's equation. Input conditions at two points to find static, dynamic, and hydrostatic pressures.

Instructions

Calculate Bernoulli's equation: P + (1/2)ρv² + ρgh = constant.

Energy conservation for flowing fluids.

Args:
    pressure1: Pressure at point 1 in Pascals
    velocity1: Flow velocity at point 1 in m/s
    height1: Height at point 1 in meters
    velocity2: Flow velocity at point 2 in m/s (optional)
    height2: Height at point 2 in meters (optional)
    fluid_density: Fluid density in kg/m³ (default 1000 for water)
    gravity: Gravitational acceleration in m/s² (default 9.81)

Returns:
    Dict containing:
        - total_pressure_1: Total pressure at point 1
        - static_pressure_1: Static pressure component
        - dynamic_pressure_1: Dynamic pressure component
        - hydrostatic_pressure_1: Hydrostatic pressure component
        - pressure2: Pressure at point 2 (if velocity2/height2 given)

Example - Water tank with outlet:
    result = await calculate_bernoulli(
        pressure1=101325,  # Atmospheric at top
        velocity1=0,  # Still water
        height1=10,  # 10m height
        velocity2=14,  # Exit velocity
        height2=0,  # Ground level
        fluid_density=1000
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pressure1Yes
velocity1Yes
height1Yes
velocity2No
height2No
fluid_densityNo
gravityNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It thoroughly explains the parameters, units, default values, and return structure. However, it does not mention error handling, units conversion, or performance characteristics, which is acceptable for a pure calculation tool.

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 formula, parameter list, return keys, and an example. It is slightly lengthy but each part adds value. The use of docstring-style formatting aids readability. Could be trimmed slightly, but overall efficient for the complexity.

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 no output schema, the description explains the return dictionary keys and their meaning. The example is realistic and covers typical usage. All parameters are documented. The tool has moderate complexity with 7 parameters, and the description provides sufficient context for an agent to use it correctly.

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%, but the description adds full semantics: each parameter has units, explanation, and context (e.g., 'pressure1: Pressure at point 1 in Pascals'). The default values and optional nature of velocity2/height2 are clearly stated. This fully compensates for the missing schema descriptions.

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 it calculates Bernoulli's equation and provides the formula. The title is null but the name 'calculate_bernoulli' combined with the equation and explanation leaves no ambiguity about the tool's purpose. It is distinct from the many other physics calculation tools by focusing on Bernoulli's principle for fluid flow.

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 includes an example but does not explicitly state when to use this tool versus alternatives like calculate_venturi_effect or calculate_pressure_at_depth. Usage is implied by the equation's domain but no when-not-to-use or comparison to siblings is provided.

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