Skip to main content
Glama
tresor4k

macalc

calculate_pendulum_period

Compute the period of a simple pendulum for physics homework or clock design. Input pendulum length in meters and optional gravity (default 9.81 m/s²) to get the period in seconds.

Instructions

Compute simple pendulum period T=2π√(L/g). Use for physics homework or clock design. Inputs: length m, gravity m/s² (default 9.81). Returns period in seconds. See list_bundles for related 'science' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
length_mYesPendulum length meters
gravityNoGravity m/s²

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

With no annotations, the description adequately covers behavior: it is a simple computation with no side effects, returns period in seconds. It does not mention permissions or limitations, but for a calculation tool this is sufficient.

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?

Three sentences, each with specific information. The first sentence states the purpose and formula, the second gives use cases, the third mentions related tools. Could be slightly more concise, but efficient overall.

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

Completeness5/5

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

For a simple two-parameter tool with an output schema, the description is complete: formula, inputs with defaults, output in seconds, and pointer to related tools. There are no gaps given the context signals.

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

Parameters4/5

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

Input schema provides 100% coverage with descriptions. The description adds value by specifying units (length m, gravity m/s²), default gravity (9.81), and the formula, which clarifies parameter roles beyond the schema.

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

Purpose5/5

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

Description explicitly states the tool computes the period of a simple pendulum using the formula T=2π√(L/g), with clear use cases like physics homework or clock design. This leaves no ambiguity about what it does and distinguishes it from the many other 'calculate_' tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides specific use cases ('physics homework or clock design') and mentions related 'science' calculators via list_bundles. It does not explicitly state when not to use it, but the clarity of purpose implicitly guides selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server