Skip to main content
Glama

Kinetic Energy Calculator

calculator_kinetic_energy
Read-only

KE = ½ m v² (Joules).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mass": "<mass>",
      "velocity": "<velocity>"
    },
    "name": "calculator_kinetic_energy"
  }
}

Input Schema

NameRequiredDescriptionDefault
massYesMass in kg.
velocityYesVelocity in m/s.

Output Schema

NameRequiredDescriptionDefault
resultYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so the safety profile is covered. The description adds that the result is expressed in Joules (SI), which is useful context, but says nothing about precision, rounding, or edge cases such as negative or zero values.

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?

A single front-loaded line with zero filler, which is appropriate for a trivial two-input calculator. It is arguably over-terse rather than padded, so nothing is wasted.

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?

With an output schema, 100% parameter coverage, and annotations covering safety, an agent has everything needed to call this simple pure calculator correctly; the description just names the formula and unit. Only minor gaps (usage routing, numeric edge cases) remain.

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

Parameters3/5

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

Schema description coverage is 100% (mass in kg, velocity in m/s), so the schema already documents both parameters fully. The formula adds the relationship between them and the output unit, but no additional per-parameter meaning; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The formula 'KE = ½ m v²' with the unit '(Joules)' pins down exactly what is computed from the two inputs, which distinguishes it from siblings like calculator_potential_energy (mgh) or calculator_energy. It stops short of stating a verb like 'computes', relying on the tool name to carry that, so it is clear but not fully self-contained.

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?

There is no statement of when to choose this over calculator_energy, calculator_potential_energy, or calculator_physics_work — the formula only implies the domain. An agent must infer usage entirely from the name and formula.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.