Skip to main content
Glama

Semana ISO de una fecha

date-iso-week
Read-onlyIdempotent

Convierte una fecha a semana ISO 8601 (AAAA-Www-D) o una semana ISO a su rango de fechas. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: describir un año y mes (month-info). 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 date to its ISO 8601 week date (YYYY-Www-D) or an ISO week (year + week) to its Monday-Sunday date range; also reports weeks in that ISO year. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: describing a year and month (month-info). 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.

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": {
      "date": "2026-10-31"
    },
    "name": "date-iso-week"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate to convert (string; optional; up to 10 chars; format date).
weekNoISO week 1-53 (integer; optional; min 1; max 53).
iso_yearNoISO week-numbering year (integer; optional; min 1; max 9999).

Output Schema

NameRequiredDescriptionDefault
endNo
isoNo
weekNo
startNo
weekdayNo
iso_yearNo
weeks_in_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "date": "2026-10-31"
      +  }
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds genuinely new operational context: no network, no stored state, determinism guarantee, and concrete limits (64 KB input, 1 s per call, 1 MB result). Those limits and the no-network claim are not derivable from any structured field.

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?

Well front-loaded and labeled (Cuándo / No para / Efectos secundarios / Límites), which makes scanning easy. However, the Spanish and English blocks are near-verbatim duplicates, so roughly half the tokens repeat information an agent only needs once.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full annotation coverage and 100% parameter descriptions, the description covers purpose, routing, side effects and limits adequately for a small pure-calculation tool. The only residual gap is the unstated behavior for an empty argument set, given all three parameters are optional.

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, but the description adds the mode mapping the schema does not: pass date for date→week, and pass year + week together for week→range. What it does not clarify is the behavior when all three optional parameters are omitted, or which mode triggers the 'weeks in that ISO year' output.

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 two concrete resources: converts a date to an ISO 8601 week date (YYYY-Www-D), or an ISO week (year + week) to its Monday-Sunday range. It also names the sibling it is not for (month-info), so an agent can separate it from the calendar/date cluster without opening the 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?

Provides explicit 'Cuándo' conditions (exact date/time-zone/calendar results: offsets, DST, month ends, leap years) and an explicit 'No para' exclusion routing to month-info. This is the when/when-not/alternative structure at full strength.

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