Skip to main content
Glama
tresor4k

macalc

calculate_pendulum_period

Compute the period of a simple pendulum given length and gravity. Use for physics homework or clock design calculations.

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?

Describes inputs (length, gravity with default) and output (period in seconds). With no annotations, the description fully covers the tool's behavior, though it could mention that it's a pure calculation with no side effects.

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?

Two focused sentences plus a reference to bundles. No wasted words, formula front-loaded for quick understanding.

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 2-parameter calculator, the description fully explains purpose, inputs, output, and hints at related tools. Output schema exists, so return format is already defined.

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?

Schema covers both parameters (100% coverage). Description adds value by repeating units and explaining the formula, which goes beyond the schema descriptions.

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?

Clearly states it computes the pendulum period using the formula T=2π√(L/g) and specifies use cases (physics homework, clock design), distinguishing it from many sibling calculation 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?

Provides context for use (physics homework, clock design) and hints at alternatives via 'See list_bundles for related science calculators', but lacks explicit when-not or exclusions.

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