Skip to main content
Glama
Sign In

Vitamin D Explorer

by app.getvitamind
OverviewDiscussionsAdmin

get_vitamin_d_year

The WHOLE YEAR of solar vitamin D for a location in a single call. monthsWithSun lists every month with at least one viable day (season edges count as partial months, see byMonth[].viableDays); solidMonths lists months where most days work; exactViableSpan gives the exact season boundaries; summary carries per-year aggregates for comparing places. Use this for any question about months, seasons, winter/summer or 'when during the year can I…' — never probe individual dates with get_vitamin_d_window for that.

Input Schema

NameRequiredDescriptionDefault
ageNoAge in years (synthesis declines with age); omit for adult baseline
latYesLatitude in decimal degrees
lonYesLongitude in decimal degrees
skinTypeNoFitzpatrick skin type 1 (very fair) to 6 (very dark); default 3
targetIUNoVitamin D target per session in IU; default 1000
timezoneNoIANA timezone like 'Europe/Madrid'. Strongly recommended — without it all times are UTC
placeNameNoThe place's name as the user said it — used to caption the chart
elevationMNoGround elevation in metres (UV rises ~8%/km); default sea level
exposedSkinFractionNoSkin exposed: 0.10 face+hands, 0.18 face+arms, 0.25 t-shirt+shorts (default), 0.40 swimsuit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • addedInput schema / properties / placeName
      Added value: +{
+  "description": "The place's name as the user said it — used to caption the chart",
+  "maxLength": 60,
+  "minLength": 1,
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it partly does so by disclosing the result shape (monthsWithSun, solidMonths, exactViableSpan, summary) and the semantics of partial months via byMonth[].viableDays. It stops short of cost/latency or precision caveats and says nothing about how optional profile parameters change results.

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?

Front-loaded with the one-call whole-year scope, then two sentences that each earn their place: one defines the output fields, one routes usage. No filler.

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?

With nine parameters, no annotations and no output schema, the description compensates by explaining the four key return fields and their edge semantics. It remains silent on what the optional physiological parameters change, which is the main remaining gap.

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 description coverage is 100%, so the schema already explains all nine parameters, including defaults for skinType, targetIU and exposedSkinFraction. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb+resource+scope: 'The WHOLE YEAR of solar vitamin D for a location in a single call.' It also explicitly distinguishes itself from the sibling get_vitamin_d_window, so an agent can separate the two without opening either schema.

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?

Gives an explicit when-to-use list (months, seasons, winter/summer, 'when during the year can I…') and an explicit when-not ('never probe individual dates with get_vitamin_d_window for that'), naming the alternative and the condition that selects it.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources