Calcgrid

Kinetic Energy Calculator

calculate_kinetic_energy

Read-onlyIdempotent

Use this when you need the energy of motion of an object of known mass and speed (vehicle, projectile, ball), for example to compare impact or braking energies. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when rotation contributes significantly (rotational energy ½·I·ω² is not included), speeds approach the speed of light (relativistic formula needed), or you need energy from height (use potential-energy). What it computes: Computes the translational kinetic energy of a moving mass from KE = ½·m·v², reported in joules, kilojoules, kilowatt-hours and kilocalories. Inputs: mass_kg (number, kg); velocity_m_s (number, m/s). Complete JSON argument examples: {"mass_kg":1200,"velocity_m_s":25} | {"mass_kg":0.145,"velocity_m_s":40} Outputs: kinetic_energy_j [J], kinetic_energy_kj [kJ], kinetic_energy_kwh [kWh], kinetic_energy_kcal [kcal], velocity_km_h [km/h]. Formula: KE = ½ × mass_kg × velocity_m_s²; kJ = J / 1000; kWh = J / 3,600,000; kcal = J / 4184 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/kinetic-energy with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/physics/kinetic-energy.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mass_kg`	Yes	Mass of the moving object in kilograms. Unit: kg.
`velocity_m_s`	Yes	Speed in metres per second (km/h ÷ 3.6, mph × 0.44704). Limited to 10 % of the speed of light, below which the classical formula is accurate to within 1 %. Unit: m/s.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`links`	No
`result`	Yes
`request`	Yes
`sources`	No
`success`	Yes
`version`	No
`freshness`	No
`timestamp`	Yes
`next_actions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

addedInput schema / examples

Added value: +[
+  {
+    "mass_kg": 1200,
+    "velocity_m_s": 25
+  },
+  {
+    "mass_kg": 0.145,
+    "velocity_m_s": 40
+  }
+]

AddedSep 25, 2026
RemovedSep 25, 2026
First observedSep 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it reports results in multiple units (J, kJ, kWh, kcal), includes a velocity conversion output (velocity_km_h), and provides a direct REST fallback path. It does not contradict annotations.

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 clear sections (when to use, when not to use, what it computes, inputs, outputs, formula, REST fallback). It is longer than minimal, but every section adds practical information for an agent. The front-loaded usage guidance is the most important part and appears first.

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?

The description is complete for a calculation tool: it covers the formula, input units, output units, example JSON, and even a REST fallback. The output schema exists, so return values are already structured. The only minor gap is that it doesn't explicitly state the precision/rounding behavior, but that is not essential for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters well. The description adds value by restating the formula, giving complete JSON examples, and clarifying the velocity conversion (km/h ÷ 3.6, mph × 0.44704) in the schema. The description also reinforces the physical meaning of each parameter.

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 states a specific verb ('compute'), a specific resource ('translational kinetic energy of a moving mass'), and the formula (KE = ½·m·v²). It also distinguishes itself from potential-energy and rotational-energy cases, making it easy for an agent to select this tool over siblings like calculate_bmi or calculate_compound_interest.

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

Usage Guidelines5/5

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

The description explicitly says when to use the tool ('when you need the energy of motion of an object of known mass and speed'), and when not to use it (rotation, relativistic speeds, height/potential energy). It even names the alternative concept (potential-energy) and instructs the agent to call the tool directly rather than answering from memory.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calcgrid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?