Skip to main content
Glama
tresor4k

macalc

calculate_sun_exposure

Calculate safe sun exposure time using UV index and Fitzpatrick skin type. Get personalized recommendations, SPF30 duration, and UV risk level.

Instructions

Calculate safe sun exposure time based on UV index and Fitzpatrick skin type. Returns: {skin_description, safe_exposure_minutes, with_spf30_minutes, uv_risk_level, recommendations}. See list_bundles for related 'voyage' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uv_indexYesUV index at destination (1–11+)
skin_typeYesFitzpatrick skin type: 1=very fair, 6=very dark

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 must cover behavioral traits. It lists the output fields but does not disclose side effects, auth requirements, or data handling (e.g., stateless computation). The mention of output fields adds some transparency.

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 concise: two sentences with no wasted words. It front-loads the purpose and efficiently lists output fields and a cross-reference.

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 calculator, the description covers the input, purpose, and output fields. It also references related tools. Lacks detail on interpreting output values, but overall adequate.

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%, and the description repeats the parameter names ('UV index and Fitzpatrick skin type') without adding new semantic details beyond what the schema already provides.

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

Purpose4/5

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

The description clearly states the tool calculates safe sun exposure time based on UV index and skin type. It mentions output fields and a related tool, but does not explicitly differentiate from the sibling 'calculate_sunscreen_reapply', which serves a similar purpose.

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 implies usage for computing sun exposure time and references related 'voyage' calculators. However, it lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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