Vitamin D Explorer

configure_sun_profile

Show the user an interactive form for the four values every other tool assumes — Fitzpatrick skin type, fraction of skin exposed, age and target IU — with the minutes they need updating live. Use this when those values are unknown, when the user wants to change them, or instead of asking for them one at a time in conversation. Whatever the user picks comes back into the conversation; pass those values explicitly to the other tools afterwards.

Input Schema

TableJSON Schema

Name	Required	Description
`age`	No	Age in years (synthesis declines with age); omit for adult baseline
`lat`	No	Latitude of the place being discussed, so the live estimate uses today's real UV there
`lon`	No	Longitude, paired with lat
`skinType`	No	Fitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
`targetIU`	No	Vitamin D target per session in IU; default 1000
`timezone`	No	IANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC
`placeName`	No	How to label that place in the widget
`exposedSkinFraction`	No	Skin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit

TDQS

A4.6/5.0

Behavior4/5

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

The description explains the tool shows a form and returns values back to the conversation, and that it updates live. It does not state whether the tool has side effects (e.g., saves profile permanently) but given no annotations, the description still provides sufficient transparency for a configuration form.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose but front-loads the core purpose. Every sentence adds value; however, it could be slightly more concise without losing clarity.

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?

Given the tool has 8 parameters, no output schema, and no annotations, the description is highly complete: it explains what the tool does, when to use it, what parameters affect live updates, and how to use the results. There is no obvious gap.

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?

While schema description coverage is 100% (baseline 3), the description adds meaning by highlighting the four main values (Fitzpatrick, skin fraction, age, target IU) and explaining that lat/lon/timezone/placeName enable a live UV estimate. This goes beyond the schema's brief 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?

The description explicitly states the tool shows an interactive form for the four key values (Fitzpatrick skin type, fraction of skin exposed, age, target IU) with live updates of minutes needed. This clearly distinguishes it from siblings that assume these values are already known.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: use when values are unknown, when the user wants to change them, or instead of asking for them one at a time. It also instructs to pass the returned values to other tools afterwards.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vitamin D Explorer tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose: year comparison vs. single-year vs. single-day vs. multi-day forecast vs. pure sun times vs. current status; personal history/profile tools are cleanly separated from public location tools. No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_, set_, log_, search_, update_, configure_, estimate_, compare_). This makes the toolset highly predictable and easy to navigate.

Tool Count4/5

At 15 tools, the count sits at the upper edge of the ideal range, but each tool carves out a distinct niche within the vitamin D/sun exposure domain. The scope is broad, yet no tool feels extraneous; a slightly lower score reflects the borderline-high number.

Completeness4/5

The domain is well covered: location search, sun times, vitamin D windows for day/year/forecast, session estimation, personal profile read/update, history logging and correction. Minor gaps exist (e.g., no favourite city management, no way to delete history), but core workflows are fully supported.

Resources

Need Help?