Skip to main content
Glama

Linear spring energy

bpj_eng_spring_compression
Read-onlyIdempotent

Calculate force and stored energy from linear spring stiffness and compression within the elastic range.

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": {
      "stiffness": "<stiffness>",
      "travel": "<travel>"
    },
    "name": "bpj_eng_spring_compression"
  }
}

Input Schema

NameRequiredDescriptionDefault
travelYes
stiffnessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world calculation, so the safety profile is covered. The description adds the meaningful behavioral caveat that results are only valid 'within the elastic range,' which is useful context beyond the annotations. It does not, however, state that no validation is performed for out-of-range inputs or describe the response shape.

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

Conciseness5/5

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

A single, front-loaded sentence with no filler; every clause (force, energy, stiffness, compression, elastic range) contributes necessary information.

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?

For a two-parameter deterministic calculator with no output schema, the definition is nearly complete: it names both outputs and the validity domain, and annotations cover side effects. Minor remaining gaps are output units and behavior for inputs exceeding the elastic range.

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 0%, so the description must carry the burden; it does map the two inputs conceptually ('stiffness' and 'compression'), and the schema titles supply units (N/mm and mm). It adds nothing about sign convention, whether compression is entered as a positive magnitude, or the units of the returned force/energy, leaving gaps the schema does not close.

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 gives a specific verb ('Calculate'), names the two quantities returned (force and stored energy), the two inputs (stiffness and compression), and the domain constraint (linear spring, elastic range). An agent can tell this is a static spring calculator rather than a dynamics or resonance tool. It stops short of explicitly contrasting with siblings such as bpj_eng_mass_spring_resonance.

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?

Usage is implied by the physics: use it for a linear spring operating within its elastic range. There is no explicit when-to-use vs. when-not guidance, no pointer to related tools (resonance, unit conversion), and no statement about what happens outside the elastic range.

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.