Skip to main content
Glama
tresor4k

macalc

calculate_projectile_motion

Solve for projectile motion: input velocity, angle, and height to get range, maximum height, and time of flight. Essential for physics and ballistics.

Instructions

Compute projectile trajectory: range, max height, time of flight. Use for physics or ballistics. Inputs: initial velocity, launch angle, height. Returns range, peak, flight time. See list_bundles for related 'science' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
velocityYesInitial velocity m/s
angle_degYesLaunch angle degrees
heightNoInitial height m

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?

With no annotations, the description carries full burden. It lists inputs and outputs but omits assumptions (e.g., no air resistance, standard gravity) or limitations (e.g., effects of extreme values). Basic behavior is covered, but important context is missing.

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?

The description is extremely concise: three short sentences with no fluff. The purpose is front-loaded in the first sentence, and every sentence adds value.

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?

Given the existence of an output schema and the tool's moderate complexity, the description is mostly complete. It lists all key outputs and inputs. However, missing assumptions about physics model slightly detract from completeness.

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

Parameters3/5

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

Schema coverage is 100% with descriptions. The description repeats input names without adding new meaning. Baseline of 3 is appropriate as description adds no extra semantic value 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 projectile trajectory with specific outputs: range, max height, time of flight. It uses the verb 'Compute' and specifies the resource ('projectile trajectory'), distinguishing it from siblings by mentioning 'physics or ballistics'.

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 description advises using for 'physics or ballistics' but does not explicitly state when not to use or name alternatives. The suggestion to 'see list_bundles for related science calculators' provides indirect guidance but lacks clear exclusions or comparisons.

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