Skip to main content
Glama

Día juliano

julian-day
Read-onlyIdempotent

Convierte fecha/hora UTC a Fecha Juliana, MJD y número de día juliano, o viceversa. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: calcular la salida y puesta del sol y la duración del día para un lugar y una fecha (sun-times). 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 UTC date-time to Julian Date, Modified Julian Date and Julian Day Number, or a Julian Date back to UTC. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: computing sunrise, sunset and day length for a place and date (sun-times). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "datetime": "2000-01-01T12:00:00Z"
    },
    "name": "julian-day"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeNoUTC date-time to convert (string; optional; up to 40 chars).
julian_dateNoJulian Date to convert to UTC (number; optional; min 0; max 5373484).

Output Schema

NameRequiredDescriptionDefault
utcNo
julian_dateNo
julian_day_numberNo
modified_julian_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "datetime": "2000-01-01T12:00:00Z"
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Converts a UTC date-time to Julian Date, Modified Julian Date and Julian Day Number, or a Julian Date back to UTC. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: computing sunrise, sunset and day length for a place and date (sun-times). 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."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's restatement of read-only/no-network/no-state is partly redundant, though it adds concrete operating limits (64 KB input, 1 s per call, 1 MB result) that stay hidden otherwise. No contradiction with the annotations; the only missed opportunity is describing the output shape given both modes exist.

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?

Front-loaded with the conversion statement, then when/when-not, then side effects and limits — a logical order with no filler sentences. Minor deduction for the duplicated Spanish/English body and the trailing self-referential artifact '[EN completo / full EN: inputSchema.description]', which is noise rather than guidance.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. Given that, the description supplies everything else an agent needs: directionality, exclusions, determinism and hard resource 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 each parameter is already documented, and the baseline would be 3. The description adds value by framing the two parameters as an either/or conversion ('o viceversa'), which the schema does not express with required fields or oneOf, helping the agent understand it supplies one or the other.

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 a specific verb and resource in both directions (UTC date-time → Julian Date, MJD, JDN; Julian Date → UTC), naming the three output quantities. It is clearly distinguishable from sibling converters like timestamp-convert or datetime-parse because it names the exact numerical outputs it produces.

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 lists the exact situations (offsets, DST, month ends, leap years) where this beats generic date tools, and an explicit 'No para' clause names the sibling sun-times as the wrong tool for sunrise/sunset. Both the when and the when-not are given with the alternative named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources