Skip to main content
Glama

x402-kinetic-energy

Kinetic Energy: Kinetic energy. Takes mass and velocity. Returns 0.5mv^2 as result. 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-kinetic-energy"
  }
}

Input Schema

NameRequiredDescriptionDefault
massNo
velocityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / mass / description
      Removed value: -"Mass to process"
    • removedInput schema / properties / velocity / description
      Removed value: -"Velocity to process"
  2. Changed2 schema fields changed
    • addedInput schema / properties / mass
      Added value: +{
      +  "description": "Mass to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / velocity
      Added value: +{
      +  "description": "Velocity to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the exact deterministic computation plus the commercial model ('5 free trial calls per signed wallet'). It omits units for mass and velocity, how string-typed inputs are parsed, and what happens past the free trial, which are meaningful gaps for a physics calculation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core formula is front-loaded, which is good, but 'Kinetic Energy: Kinetic energy.' duplicates the name and title without adding information, and the emoji-laden pricing sentence is appended without transition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter pure calculator with no output schema, stating the formula covers most of what an agent needs to predict the result. Missing unit semantics and the paid/signed-wallet access model remain uncosted gaps given the string-typed, undescribed inputs.

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

Parameters2/5

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

Schema coverage is 0% and both parameters are bare strings with no descriptions. The description only restates the parameter names and embeds them in a formula; it adds no unit conventions (kg vs g, m/s vs km/h) or format expectations an agent would need to supply correct values.

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 description names a specific computation and its inputs/outputs: 'Kinetic energy', 'Takes mass and velocity', 'Returns 0.5*m*v^2'. The formula distinguishes it from sibling energy tools like x402-potential-energy or x402-photon-energy, though it never names them explicitly.

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 when-to-use guidance, no note on when a different energy tool would be appropriate, and no prerequisites beyond the pricing line about free trial calls. The usage context is entirely implied by the 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.

Resources