Burs-IA Utils

Timestamp Unix ↔ ISO

timestamp-convert

Read-onlyIdempotent

Convierte un timestamp Unix a ISO 8601 (detecta s, ms, µs o ns) o una fecha ISO a Unix. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: analizar una fecha/hora ISO 8601 o RFC 2822 en sus partes (datetime-parse). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Converts a Unix timestamp to ISO 8601 (auto-detecting seconds, milliseconds, microseconds or nanoseconds by magnitude, or explicit unit), or an ISO date-time to Unix seconds and milliseconds. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: parsing an ISO 8601 or RFC 2822 date-time into its parts (datetime-parse). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`unit`	No	Unit of numeric input (optional; one of: auto, s, ms, us, ns; default "auto").	auto
`value`	Yes	Unix number/numeric string, or ISO 8601 string (number or string; required; up to 40 chars).
`timezone`	No	Zone for local output (string; optional; default "UTC"; up to 64 chars).	UTC

Output Schema

Name	Required	Description	Default
`iso`	No
`unix`	No
`local`	No
`unix_ms`	No
`detected_unit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / value / examples
```
Added value: +[
+  1700000000
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Converts a Unix timestamp to ISO 8601 (auto-detecting seconds, milliseconds, microseconds or nanoseconds by magnitude, or explicit unit), or an ISO date-time to Unix seconds and milliseconds. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: parsing an ISO 8601 or RFC 2822 date-time into its parts (datetime-parse). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, no network and idempotency, but the description still adds hard value: auto-detection of s/ms/µs/ns by magnitude, and concrete limits (64 KB JSON input, 1 s per call, 1 MB output). It repeats determinism/no-state, which overlaps idempotentHint and openWorldHint=false, but the size/time ceilings are information the annotations cannot convey.

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

Conciseness3/5

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

Content is front-loaded and well labeled (Cuándo / No para / Efectos / Límites), but the entire body appears twice, in Spanish and English, with the English block truncated mid-sentence ('[EN completo / full EN: inputSchema.description]'), doubling length without added information.

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?

For a stateless conversion tool with an output schema and full annotation coverage, the description supplies everything an agent needs: input direction, unit handling, timezone note, exactness rationale, exclusion to the parser sibling, and operational limits.

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?

Schema coverage is 100%, so the baseline is 3; the description earns the extra point by explaining how the 'auto' unit works (magnitude-based detection across s/ms/µs/ns), which the enum alone does not tell the agent. It does not explain the timezone parameter's effect on output beyond the schema text.

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 concrete verbs and resources: converting a Unix timestamp to ISO 8601 (with unit auto-detection) or an ISO date-time to Unix seconds/ms. It also names the exact sibling it is not (datetime-parse), so the agent can distinguish it without opening either schema.

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?

Explicit 'Cuándo' clause gives the triggering condition (exact date/timezone/calendar results: offsets, DST, month ends, leap years) and 'No para' excludes parsing ISO/RFC 2822 into parts, naming datetime-parse as the alternative. When-to-use, when-not-to-use and the alternative are all present.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?