Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_bernoulli

Calculate fluid flow parameters using Bernoulli's equation to analyze pressure, velocity, and height relationships in fluid dynamics applications.

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?

With no annotations provided, the description carries full burden. It effectively discloses behavioral traits: it's a calculation tool (implied non-destructive), includes default values for fluid_density and gravity, and specifies the return structure. However, it doesn't mention error handling, computational limits, or assumptions like incompressible flow.

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 equation, brief context, parameter details, return values, and an example. It's appropriately sized for a 7-parameter tool. Minor improvement could be front-loading the example or trimming the equation repetition, but overall it's efficient and informative.

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?

Given the tool's complexity (7 parameters, physics calculation) and lack of annotations/output schema, the description is quite complete. It covers purpose, parameters, returns, and an example. A slight gap is no explicit mention of assumptions (e.g., steady flow) or error cases, but it's largely adequate for agent use.

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?

The schema description coverage is 0%, so the description must compensate fully. It does so excellently: each parameter is clearly defined with units (e.g., 'Pressure at point 1 in Pascals'), optional/default status is indicated, and the example illustrates practical usage. This adds significant meaning beyond the bare 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?

The description clearly states the tool's purpose: 'Calculate Bernoulli's equation: P + (1/2)ρv² + ρgh = constant.' It provides a specific verb ('calculate') and resource ('Bernoulli's equation'), and distinguishes it from sibling tools by focusing on fluid dynamics energy conservation, unlike other physics calculation tools in the list.

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 implies usage through the example (water tank with outlet) and the equation context, suggesting it's for fluid flow problems. However, it lacks explicit guidance on when to use this tool versus alternatives like 'calculate_venturi_effect' or 'calculate_pressure_at_depth' from the sibling list, leaving some ambiguity.

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