Skip to main content
Glama

Mass-spring natural frequency

bpj_eng_mass_spring_resonance
Read-onlyIdempotent

Estimate natural frequency and period of an undamped single-degree-of-freedom mass-spring system.

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>",
      "mass": "<mass>"
    },
    "name": "bpj_eng_mass_spring_resonance"
  }
}

Input Schema

NameRequiredDescriptionDefault
massYes
stiffnessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so safety context is covered. The description adds the meaningful physical constraint (undamped, SDOF) and the word "estimate" hints at approximation, but it says nothing about the formula used, output units (Hz vs rad/s, seconds), or behavior under extreme inputs near the schema bounds.

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; the core resource and its physical scope are established immediately.

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 simple two-input calculator this is close to adequate, and the absence of an output schema is not an issue since the description names the two returned quantities. The gaps are that output units/conventions are unspecified and the parameters are left entirely to the schema titles.

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 description coverage is 0% — only the titles "Mass (kg)" and "Spring stiffness (N/m)" carry unit information. The description never mentions the parameters, their units, or the fact that values must be positive and non-zero, so it does not compensate for the missing schema documentation.

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?

States a specific verb ("Estimate") and a specific resource ("natural frequency and period of an undamped single-degree-of-freedom mass-spring system"), which clearly distinguishes it from siblings like bpj_eng_spring_compression or bpj_eng_pendulum_period. It stops short of naming a sibling to contrast with, so it is clear but not maximally disambiguating.

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?

"Undamped single-degree-of-freedom" implicitly scopes when the tool applies, letting an agent rule out damped or multi-DOF problems. However, there is no explicit when-to-use statement, no prerequisite note, and no named alternative for damped cases, so guidance is implied rather than stated.

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.