fateclear-solar-time

true_solar_time

Convert clock birth time at a longitude to local true solar time with longitude correction, equation of time, and China 1986-1991 DST handling.

Instructions

Convert a clock birth time at a longitude into local true solar time (longitude correction + equation of time, China 1986–1991 DST aware).

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": {
      "datetime": "<datetime>",
      "longitude": "<longitude>"
    },
    "name": "true_solar_time"
  }
}

Input Schema

Name	Required	Description
`dst`	No
`eot`	No
`datetime`	Yes	Clock time 'YYYY-MM-DD HH:mm' or 'YYYY-MM-DDTHH:mm[:ss]'
`latitude`	No
`longitude`	Yes	East longitude in degrees, west negative
`utcOffset`	No	Clock UTC offset in hours, default 8

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose key computation details: longitude correction, equation of time, and DST awareness for China 1986–1991. However, it does not describe the return format, precision behavior, or error handling, leaving significant gaps for a computation tool with no output schema.

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 a single, front-loaded sentence with no wasted words. The parenthetical efficiently bundles the key technical qualifiers without overwhelming the reader.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with no annotations, no output schema, and only 50% schema coverage, one sentence is insufficient. It omits return value details, latitude usage, parameter option meanings, and any caveats beyond the China 1986–1991 DST window.

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 only 50%, so the description should compensate for undocumented parameters. It hints at equation of time and DST awareness, which loosely map to the eot and dst parameters, but it never explains latitude, utcOffset defaults, or the enum values for eot and dst.

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?

States a specific verb ('Convert') and resource ('clock birth time at a longitude into local true solar time'), with clarifying scope like longitude correction, equation of time, and China 1986–1991 DST awareness. It is clearly distinct from sibling tools by purpose, though it does not explicitly name solar_terms or china_dst to differentiate.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no guidance on when to use it versus alternatives such as solar_terms or china_dst. There are no exclusions, prerequisites, or selection conditions to help an agent choose among siblings.

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

Deploy Server