AgentTime — True Time & Astronomy
Server Details
Authoritative time intelligence — current time in 597 timezones, sunrise/sunset/twilight times by location (US Naval Observatory), and moon phase calendar. Essential for scientific, agricultural, and scheduling agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 3 of 3 tools scored.
Each tool targets a distinct area: get_astronomy covers sun and moon times, get_current_time provides timezone-aware current time, and get_moon_phases focuses on lunar phases. No overlap in functionality.
All tools follow a consistent get_noun pattern with snake_case (get_astronomy, get_current_time, get_moon_phases), making them predictable and easy to understand.
With only 3 tools, the server feels thin for a domain spanning both time and astronomy. While each tool is well-defined, the count is borderline low for the broad scope implied by the server name.
The surface covers basic time lookup and sun/moon data, but lacks many expected astronomy features such as planets, star positions, eclipses, or equinoxes. Significant gaps exist for a server claiming 'Astronomy'.
Available Tools
3 toolsget_astronomyBInspect
Get sunrise, sunset, and twilight times for any location using US Naval Observatory data. Also returns moonrise and moonset.
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | UTC offset in hours (e.g. -5 for EST, 1 for CET). Default: 0 (UTC) | |
| lat | No | Latitude (default: 40.7128 — New York City) | |
| lon | No | Longitude (default: -74.0060 — New York City) | |
| date | No | Date in YYYY-MM-DD format (default: today) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions using US Naval Observatory data but does not disclose limitations such as date range validity, error handling for invalid coordinates, or network dependency. Minimal transparency beyond the basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the core purpose (sunrise/sunset/twilight) and then extends to moonrise/moonset. Every sentence adds value, no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the tool has all parameters documented, there is no output schema. The description does not mention the format or structure of the returned times (e.g., whether in UTC or local time), nor does it clarify if the tool returns a single timeset per day or a range. Adequate but with gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so each parameter (tz, lat, lon, date) is already documented with defaults and formats. The description adds no further parameter meaning beyond what the schema provides, resulting in baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: retrieving sunrise, sunset, twilight, moonrise, and moonset times for any location using US Naval Observatory data. This distinguishes it from sibling tools like get_current_time (current time only) and get_moon_phases (moon phase data).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus its siblings (e.g., get_moon_phases might be preferred for moon phase information). It does not specify prerequisites or context for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_current_timeAInspect
Get the current time in any timezone. Returns local datetime, UTC datetime, unix epoch, UTC offset, DST status, day of week, day of year, and week number.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Response format: iso (datetime only), unix (epoch only), both (default) | both |
| timezone | No | IANA timezone name (e.g. America/New_York, Europe/London, Asia/Tokyo). Defaults to UTC. | UTC |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. It lists return fields but does not mention failure modes, validation, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first states purpose, second lists return fields. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity with 2 simple parameters and no required fields, the description is adequate and provides sufficient information for use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description does not add much beyond schema; it lists return fields but no extra parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets the current time in any timezone and lists many return fields, distinguishing it from sibling astronomy tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance, but the purpose is straightforward. Lacks alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_moon_phasesAInspect
Get upcoming moon phases (New Moon, First Quarter, Full Moon, Last Quarter) and current moon illumination percentage from the US Naval Observatory.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Start date in YYYY-MM-DD format (default: today) | |
| count | No | Number of phases to return (default: 4, max: 99) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. It describes what it does (get phases, illumination) but lacks details on data freshness, rate limits, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, concise, includes key specifics (phases, illumination, source). No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description should hint at return format. It mentions phases and illumination but not structure. Adequate for simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description adds minimal extra context ('upcoming', 'illumination') beyond schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it retrieves upcoming moon phases and illumination percentage, listing specific phases and source (US Naval Observatory). Differentiates from siblings (get_astronomy, get_current_time).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for moon phase data but does not explicitly state when to use alternatives like get_astronomy or get_current_time, nor provides exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!