Skip to main content
Glama

date_add

Read-only

Add or subtract years, months, weeks, days, business days, hours, minutes, or seconds from a date, time, or Unix timestamp with IANA or city timezone support.

Instructions

Add/subtract (negative) years, months (clamped), weeks, days, business_days, hours, minutes, seconds. Times: now, today, YYYY-MM-DD[ HH:MM], DD.MM.YYYY[ HH:MM], HH:MM, unix. Zones: IANA, city, CET/PST; default local.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "date_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
hoursNo
startNo
weeksNo
yearsNo
monthsNo
minutesNo
secondsNo
timezoneNo
business_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior3/5

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

Beyond the readOnlyHint annotation the description adds real behavioral context: negative values subtract, months are clamped, and the timezone defaults to local. It still leaves gaps it is the sole source for – how fractional hours/minutes/seconds are handled, whether business_days skips weekends and holidays, and what happens when start is omitted (all 10 params are optional).

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?

Two dense, front-loaded clauses with no filler; every token carries information. The telegraphic style, though, borders on cryptic – 'Times:' and 'Zones:' are labels without predicates, forcing the agent to infer the relationship.

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

Completeness3/5

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

For a 10-parameter tool with no schema descriptions, no output schema, and only a readOnly annotation, the description covers units, input formats, and zones but omits the return value entirely and leaves business_days and fractional-unit semantics undocumented. It is adequate to attempt a call but not complete.

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 0%, so the description must carry the load, and it partially does: it documents the timezone value domain (IANA, city, CET/PST, default local) and the accepted start formats. It never names 'start' as a parameter, does not explain business_days semantics, and does not say the numeric unit params accept fractions or negatives.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the operation (add/subtract, with negative values signifying subtraction) and enumerates the supported units, which separates it from the diff-oriented sibling. What it never states outright is that the operation applies to a starting date/time and returns a new one – the object is only implied by the telegraphic 'Times:' clause.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Listing accepted input formats ('now, today, YYYY-MM-DD[ HH:MM], DD.MM.YYYY[ HH:MM], HH:MM, unix') and the default zone implicitly tells the agent the kinds of calls it can make. There is no explicit when-to-use versus date_diff, no prerequisites, and no exclusions.

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