Skip to main content
Glama
IBM

Physics MCP Server

by IBM

calculate_jerk

Calculate jerk (rate of change of acceleration) from time and acceleration data. Determine jerk vectors, average jerk, and maximum jerk magnitude for vehicle comfort analysis and mechanical design.

Instructions

Calculate jerk (rate of change of acceleration).

Jerk = da/dt is important for comfort in vehicles and mechanical design.

Args:
    times: Time values in seconds (or JSON string)
    accelerations: Acceleration vectors [[x,y,z], ...] in m/s² (or JSON string)

Returns:
    Dict containing:
        - jerks: Jerk vectors [[x,y,z], ...] in m/s³
        - average_jerk: Average jerk [x,y,z] in m/s³
        - max_jerk_magnitude: Maximum jerk magnitude in m/s³

Example:
    result = await calculate_jerk(
        times=[0, 1, 2, 3],
        accelerations=[[0,0,0], [2,0,0], [4,0,0], [6,0,0]]
    )
    # jerk_x ≈ 2 m/s³ (constant)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timesYes
accelerationsYes
Behavior2/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 describes the calculation behavior and return format, but doesn't disclose error conditions, numerical precision, handling of invalid inputs, or computational characteristics. The description provides basic operational transparency but lacks important behavioral details for a computational 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?

Well-structured with purpose statement, importance context, parameter documentation, return specification, and example. Every sentence adds value. Slightly long but appropriately so given the need to document parameters and returns without annotations or output schema. Could be more front-loaded but remains efficient.

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 2 parameters with 0% schema coverage and no output schema, the description provides complete parameter documentation and detailed return format specification. It includes an example showing correct usage. For a calculation tool without annotations, this is nearly complete - only missing some behavioral aspects like error handling or numerical methods.

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 description adds significant semantic value beyond the schema. With 0% schema description coverage, the description fully documents both parameters: 'times' as 'Time values in seconds (or JSON string)' and 'accelerations' as 'Acceleration vectors [[x,y,z], ...] in m/s² (or JSON string)'. It clarifies units, formats, and provides concrete examples, compensating completely for the schema gap.

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 jerk (rate of change of acceleration)' with a specific verb ('calculate') and resource ('jerk'). It distinguishes from siblings by focusing on jerk calculation rather than other physics calculations like acceleration, force, or energy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. While it mentions jerk is 'important for comfort in vehicles and mechanical design', it doesn't specify when to choose this over other calculation tools or what prerequisites exist. The example shows usage but lacks contextual decision-making guidance.

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