Skip to main content
Glama
tresor4k

macalc

calculate_distance_3d

Compute Euclidean distance between two 3D points. Input six coordinates (x1,y1,z1,x2,y2,z2) to get the straight-line distance using √(Δx²+Δy²+Δz²). Ideal for 3D modeling, physics, and geometry.

Instructions

Compute Euclidean distance between two 3D points. Use for 3D modeling, physics. Formula: √(Δx²+Δy²+Δz²). Inputs: x1,y1,z1,x2,y2,z2. Returns distance. See list_bundles for related 'math' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1Yes
y1Yes
z1Yes
x2Yes
y2Yes
z2Yes

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 provides the formula and lists all inputs, but it does not mention return type (though output schema exists), edge cases, or error handling. It is good but could add more behavioral context beyond formula.

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 sentences: first sentence states purpose and usage, second gives formula and inputs. Highly concise, front-loaded, no filler words.

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?

Covers purpose, usage, formula, inputs, and even points to related tools via list_bundles. With output schema existing, the description is complete for a straightforward computation tool.

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

Parameters5/5

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

Explicitly lists all six parameters (x1,y1,z1,x2,y2,z2) and explains they are coordinates for 3D points. Since schema descriptions are missing (0% coverage), the description fully compensates by clarifying the semantics.

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 Euclidean distance between 3D points with specific verb 'Compute' and mentions usage in 3D modeling and physics. The formula and inputs are provided, and it distinguishes itself from siblings by specifying 3D.

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?

Mentions use cases (3D modeling, physics) and suggests list_bundles for related calculators. It implicitly differentiates from calculate_distance_2d but lacks explicit when-not-to-use or alternative sibling names.

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