True Solar Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server performs deterministic true solar time conversion. It does not geocode addresses, store personal data, or provide astrological interpretation. Pass an IANA timezone and decimal longitude directly.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_true_solar_timeA | Convert a local civil birth time to local apparent true solar time using the supplied IANA timezone and longitude. Returns UTC, longitude correction, equation of time, DST correction, date-shift warnings, and confidence. No address lookup is performed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another. Its purpose—converting civil time to true solar time—is stated unambiguously in the description.
The single name, calculate_true_solar_time, follows a clear snake_case verb_noun pattern and precisely describes the action and target. No competing conventions exist to conflict with it.
A one-tool surface is thin even for a narrowly scoped calculation server; useful neighbors like inverse conversion or batch/multi-date processing are absent. The tool itself is non-trivial and earns its place, but the set feels minimal.
The stated forward conversion (civil time → true solar time) appears fully served, including UTC, equation of time, DST and confidence outputs. However, there is no inverse conversion (true solar → civil), no batch handling, and no related solar computations, leaving notable gaps for agents working the domain both ways.