Skip to main content
Glama

Small-angle pendulum period

bpj_eng_pendulum_period
Read-onlyIdempotent

Estimate the small-angle period and frequency of a simple pendulum under standard gravity.

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": {
      "length": "<length>"
    },
    "name": "bpj_eng_pendulum_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthYes

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 establish this as a read-only, idempotent, non-destructive computation, so the safety burden is covered. The description adds meaningful context by fixing the gravity assumption and the small-angle approximation, but says nothing about output units (seconds vs Hz) or rounding, which matters for a numeric estimator.

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 well-formed sentence with the resource and the key assumption front-loaded; nothing is redundant. It is perhaps too terse given the unstated output units, but there is no wasted wording.

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?

The tool is a one-parameter calculator with no output schema, so the description's main obligation is to say what is computed and under what assumptions — both are covered. The missing gap is output units and the parameter's physical meaning, which leaves an agent guessing at the result's scale.

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% — the only parameter ('length') has no description field, only a title and numeric bounds. The description mentions no parameters at all, so it fails to compensate or clarify that the input is the pivot-to-mass-center distance in meters rather than pivot-to-surface length.

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 verb ('Estimate') and a specific resource ('small-angle period and frequency of a simple pendulum'), and adds the governing physical assumption ('standard gravity'). It does not explicitly contrast itself with neighbors like bpj_eng_mass_spring_resonance, but the phenomenon is distinct enough to be identifiable.

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?

The phrase 'small-angle' implies the regime of validity, but the description never states when the approximation breaks down or when an exact/large-amplitude method would be needed instead. No explicit when-to-use or when-not-to-use guidance is provided.

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.