F
licenseB
qualityD
maintenanceProvides current time and timezone conversion using IANA timezone names, with automatic system timezone detection.
2
-
Timezone Truth
Server Details
Convert times between IANA zones and detect skipped or ambiguous DST local times.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 toolconvert_timeConvert a time between timezonesARead-onlyInspect
Convert a wall-clock time between two IANA timezones, and report the ways the conversion can be wrong.
ALWAYS use this instead of doing the arithmetic. Timezone conversion looks like addition and is not: the mapping from a local time to an instant is not a function.
On the spring-forward date, an hour of local time DOES NOT EXIST. Asked to convert 02:30 on that date, a model will return a plausible timestamp for a time that never happens. This tool returns null and says why.
On the fall-back date, an hour happens TWICE. There are two correct answers an hour apart; this returns both rather than silently choosing.
The gap between two zones is not constant. Zones start and end daylight saving on different dates, so a cached offset is wrong for weeks each year.
Not all offsets are whole hours: India is +05:30, Nepal +05:45.
Input: time must be YYYY-MM-DD HH:MM (or with T, and optional seconds) — free-form dates are refused rather than guessed. from and to must be full IANA names such as "America/New_York".
ABBREVIATIONS ARE REJECTED, deliberately, even though most runtimes accept them. Node resolves "BST" to Bangladesh Standard Time (UTC+06:00) when nearly everyone writing it means British Summer Time (UTC+01:00) — a five-hour error that yields a perfectly plausible timestamp. Same for CST, IST, PST, and EST.
Returns: the chosen UTC instant (null if the local time does not exist), every candidate instant, both zone readings with the offset and abbreviation that applied on THAT date, the difference between the zones, upcoming clock changes for both, and warnings. Check warnings for severity "error" before using the result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target zone as a full IANA name, e.g. "Asia/Tokyo". | |
| from | Yes | Source zone as a full IANA name, e.g. "America/New_York". Abbreviations like BST, CST, IST, PST and EST are REJECTED because they are ambiguous. | |
| time | Yes | Wall-clock time as YYYY-MM-DD HH:MM (T separator and seconds also accepted). Do NOT include an offset or zone in the string. Free-form dates such as "next Tuesday" are refused rather than guessed. | |
| prefer | No | Which occurrence to use when the local time happens twice (a fall-back hour). Defaults to the earlier one. Both are always returned in candidates. |
TDQS
A5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behavioral traps well beyond the readOnlyHint: nonexistent local times return null, ambiguous fall-back hours return both candidates, zone gaps vary over time, and abbreviations are deliberately rejected because of real-world ambiguity. It also tells the agent to check 'warnings' for severity 'error' before trusting the result.
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 long but every section earns its place: purpose, edge cases, input constraints, rejected abbreviations, and return format. Key guidance is front-loaded with 'ALWAYS use this instead of doing the arithmetic', and the bulleted pitfalls are organized for quick comprehension.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Even without an output schema, the description enumerates what is returned: the chosen UTC instant, all candidates, zone readings with offsets and abbreviations, the zone difference, upcoming clock changes, and warnings. Combined with 100% schema coverage and no sibling tools, nothing an agent needs to call this correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although schema coverage is 100%, the description adds substantive meaning: strict YYYY-MM-DD HH:MM format, refusal of free-form dates, full IANA names for from/to, and a concrete example of why abbreviations fail ('BST' resolving to Bangladesh Standard Time instead of British Summer Time). The prefer parameter's behavior with dual candidates is also reinforced.
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 the exact verb 'convert' and the resource 'wall-clock time between two IANA timezones', and immediately distinguishes itself from ad-hoc arithmetic via 'ALWAYS use this instead of doing the arithmetic'. This is precise and unambiguous even without sibling tools.
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?
Explicitly tells the agent when to use this tool and what to avoid: 'ALWAYS use this instead of doing the arithmetic.' It also provides strong exclusions, such as free-form dates being refused and abbreviations being rejected, so an agent knows the acceptable usage envelope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
convert_time
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.
Time zone conversion, meeting-slot finding across countries, DST checks and .ics invites. All.
1Deterministic time tools for AI agents: timezone conversion, business-day math, cron interpretation.
Validates cron expressions and finds DST bugs that make jobs silently skip or double-fire.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides current time and timezone conversion using IANA timezone names, enabling LLMs to get time information and convert times between timezones.MIT
- AlicenseNot gradedqualityCmaintenanceProvides time zone management utilities including retrieving current time in any global time zone and converting time between different time zones with automatic daylight saving time handling.73MIT
- AlicenseBqualityDmaintenanceProvides current time information and timezone conversion capabilities using IANA timezone names. Enables LLMs to get current time in any timezone and convert times between different timezones with automatic system timezone detection.2MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.9/5.0
Disambiguation5/5
With only one tool, there is no ambiguity or overlap to confuse an agent. The tool's purpose is clearly scoped to timezone conversion.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern: convert_time. There are no conflicting conventions to create inconsistency.
Tool Count3/5
A single tool feels thin for an MCP server, even for a narrow domain. However, timezone conversion is a focused task, so the count is borderline rather than inappropriate.
Completeness5/5
The tool fully addresses the complexities of timezone conversion: nonexistent times, ambiguous times, variable offsets, abbreviation pitfalls, and clock changes. It leaves no major gaps within its stated purpose.