Skip to main content
Glama
tresor4k

macalc

calculate_radioactive_decay

Calculate remaining quantity after radioactive decay using the formula N = N0 * 0.5^(t/half-life). Input initial amount, half-life, and elapsed time for physics or carbon dating.

Instructions

Compute remaining quantity after radioactive decay. Use for physics or carbon dating. Formula: N=N0·(0.5)^(t/half-life). Inputs: initial qty, half-life, elapsed time. Returns remaining qty. See list_bundles for related 'science' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initialYesInitial amount
half_lifeYesHalf-life
timeYesTime elapsed

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.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the formula and inputs but does not mention edge cases (e.g., time=0) or error conditions. Basic behavior is covered, but not deeply.

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?

Three sentences, each purposeful: tool purpose, formula and inputs, and reference to related tools. No redundant information, making it efficient and well-structured.

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 simple physics calculation with an output schema present, the description covers the essential aspects: purpose, formula, inputs, and even a cross-reference. It does not detail output formatting, but that is acceptable given the output schema.

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 coverage is 100% with descriptions for all three parameters. The description adds the formula N=N0·(0.5)^(t/half-life) and clarifies that inputs are initial qty, half-life, and elapsed time, enhancing understanding beyond 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?

The description clearly states the tool computes remaining quantity after radioactive decay, specifying the formula and use cases like physics or carbon dating. It distinguishes itself from sibling tools (e.g., calculate_caffeine_half_life) by being a dedicated physics calculation.

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 explicitly says 'Use for physics or carbon dating' and references list_bundles for related science calculators, providing clear context and pointing to alternatives. It does not explicitly exclude other uses, but the guidance is adequate.

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