Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

time_iso_8601_formatter

Read-onlyIdempotent

Parse, format, and perform arithmetic on ISO 8601 and RFC 3339 dates, times, durations, intervals, and recurring intervals with strict validation.

Instructions

ISO 8601 / RFC 3339 Date Formatter. Parse, format, and do arithmetic on ISO 8601 / RFC 3339 dates, times, durations, intervals, and recurring intervals using a strict hand-rolled parser (the permissive native Date parser is deliberately avoided). The 'operation' field selects the mode: 'parse' decodes one ISO string into calendar/ordinal/week-date components, offset, epoch milliseconds, and UTC; 'format' renders date fields or a unix-ms value into a chosen ISO style; 'duration' normalises an ISO duration into canonical form, human text, and total seconds; 'add' applies a duration to a base instant with calendar-aware month wrapping; 'now' returns the current UTC instant. Use this for ISO/RFC string parsing and rendering, not time_timezone_converter (IANA zone-to-zone wall clock with DST), time_world_clock (live multi-city clock), or convert_timestamp (unix-epoch to human date). Pure read-only computation, no network or storage; only 'now' reads the wall clock. Rate limit 60 requests/minute per client (anonymo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesMode to run. 'parse' decodes an ISO string; 'format' renders to an ISO style; 'duration' normalises an ISO duration; 'add' adds a duration to a base instant; 'now' returns the current UTC instant (ignores all other fields).parse
inputNoOperation payload. For 'parse' an ISO 8601 string (e.g. 2026-05-26T14:30:00+02:00, 2026-W22-2, P1Y2M3DT4H5M6S, or start/end). For 'format' a unix-milliseconds number or an object with year, month, day and optional hour/minute/second/ millisecond/offsetMinutes (or unixMs). For 'duration' an ISO duration string, a seconds number, or a duration object. Unused by 'add' and 'now'.
styleNoOutput style for 'format' only. 'rfc3339' forces a trailing Z when no offset is given.extended
baseNoBase date or datetime for 'add' (ISO 8601). Must be a date or datetime, not a duration or interval.
durationNoISO 8601 duration to add for 'add' (e.g. P1M, PT1H30M, -P10D). Leading minus subtracts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the operation succeeded.
operationNoThe operation that was run (echoed back).
resultNoOperation-specific output. parse returns input, kind (date/time/datetime/duration/interval/recurring), and optional date/time/offset/epochMs/utc/duration/ seconds/start/end fields. format returns iso. duration returns iso, human, seconds. add returns iso, utc. now returns isoUtc, isoLocalLike, epochMs.
errorNoError message when success is false.
Behavior5/5

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

The description discloses key behavioral traits: it's a pure read-only computation with no network/storage (only 'now' reads wall clock), uses a strict hand-rolled parser, and aligns with annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is comprehensive but slightly long; however, every sentence is informative. It front-loads the core purpose and then details operations. It could be more concise, but the structure is logical and readable.

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?

Given the tool's complexity (5 parameters, multiple operations, sibling tools), the description is thorough. It covers all operations, input/output behaviors (with output schema existing), and provides sufficient context for an agent to use it correctly. No major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 100% and the input schema already describes parameters, the description adds value by explaining operation-specific input expectations (e.g., 'for parse: an ISO 8601 string...'). This contextualizes the parameters beyond basic type/description.

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 clearly states the tool's purpose as an ISO 8601 / RFC 3339 date formatter, listing five specific operations (parse, format, duration, add, now). It also explicitly distinguishes this tool from siblings like time_timezone_converter, time_world_clock, and convert_timestamp, providing clear differentiation.

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?

The description provides explicit guidance on when to use this tool versus alternatives, stating 'Use this for ISO/RFC string parsing and rendering, not...' and names three sibling tools with their purposes. It also mentions the rate limit of 60 requests/minute, helping agents choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server