Skip to main content
Glama
True Solar Time MCP Server

True Solar Time MCP Server

calculate_true_solar_time

Read-onlyIdempotent

Convert a local civil birth time to local apparent true solar time using an IANA timezone and longitude; returns UTC plus longitude, equation-of-time, and DST corrections.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "timezone": "<timezone>",
      "longitude": "<longitude>"
    },
    "name": "calculate_true_solar_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesLocal civil date in YYYY-MM-DD format.
timeYesLocal civil time in HH:mm format.
latitudeNoOptional birth latitude in decimal degrees.
timezoneYesIANA time zone, for example Asia/Shanghai or America/Los_Angeles.
longitudeYesBirth longitude in decimal degrees, east positive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by enumerating the derived outputs — UTC, longitude correction, equation of time, DST correction, date-shift warnings, confidence — plus the no-address-lookup constraint. It stops short of describing failure behavior for invalid or ambiguous timezones.

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?

Three tight sentences: the operation first, the return payload second, the scope limitation last. Nothing repeats the name, and there is 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 no output schema, the description usefully lists what comes back, and the annotations handle the safety profile for this 5-parameter tool. The remaining gap is limited to the role of the optional latitude and edge-case behavior on invalid timezone input.

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%, so date, time, timezone, longitude, and optional latitude are already documented in the schema. The description reinforces timezone and longitude as the drivers of the conversion but adds no new meaning, and never explains why latitude is optional or how it influences the result.

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 names a precise verb-and-resource pair: convert a local civil birth time into local apparent true solar time. It also pins down the required inputs (IANA timezone, longitude), so an agent knows exactly what this tool computes rather than guessing at a generic time conversion.

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?

The closing line 'No address lookup is performed' sets an explicit boundary, telling the agent this tool will not resolve a place name and that coordinates must be supplied some other way. It does not name an alternative tool for geocoding, but no siblings exist to route to, so context is clear rather than exclusionary.

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

Deploy Server

Other Tools