TeamPredict HR Calculators

Add or subtract days, hours and minutes from a date-time

add_time_to_datetime

Read-onlyIdempotent

Move a date and clock time forward or back by days, hours and minutes in a US time zone and get the resulting date and time. Days move the calendar date and keep the clock time (the way a phone calendar does); hours and minutes are counted as they really pass, so a daylight saving change inside the span is handled. Use time_duration_between instead to measure the gap between two known date-times, add_to_date for calendar years, months and weeks, and convert_time_zone to show a moment in other zones.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "start_time": "<start_time>"
    },
    "name": "add_time_to_datetime"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Days to move. Default 0.
`hours`	No	Hours to move. Default 0.
`minutes`	No	Minutes to move. Default 0.
`direction`	No	add to move forward, subtract to move back. Default add.	add
`time_zone`	No	The time zone the clock times are read in, so a span across a daylight saving change counts the hour that really passes. Use 'none' for plain 24-hour days with no zone. Default America/New_York.	America/New_York
`start_date`	Yes	The date to start from as a calendar date in the form YYYY-MM-DD, for example 2026-11-02.
`start_time`	Yes	The time to start from as a 24-hour clock time in the form HH:MM, for example 22:30.

Output Schema

Name	Required	Description
`inputs`	Yes	The inputs as used, with defaults filled in.
`results`	Yes	The computed numbers. Unavailable numbers are null.
`summary`	Yes	One or two plain sentences with the headline numbers.
`calculator_url`	Yes	The TeamPredict calculator page that shows the same calculation, where a person can change the inputs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds genuinely valuable semantics beyond them: days shift the calendar date and preserve clock time while hours/minutes count real elapsed time, so DST transitions inside the span are handled correctly. It does not cover range limits or error behavior, which keeps it short of a 5.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and result, then the semantic rule, then the routing alternatives. No filler and nothing repeated from the schema.

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?

Annotations carry the safety profile, an output schema exists so return format need not be described, and all seven parameters are documented in the schema. What remains for the description — the DST/calendar-day semantics and sibling routing — is exactly what it covers.

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 and the schema already defines each parameter. The description nonetheless adds meaning the schema does not: the days-versus-hours semantic distinction and the consequence of the time_zone parameter (real elapsed vs. plain 24-hour days).

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 concrete verb+resource: move a date and clock time forward or back by days, hours and minutes, and return the result. It immediately scopes itself to US time zones, which separates it from any generic date-arithmetic sibling.

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?

Names three alternatives (time_duration_between, add_to_date, convert_time_zone) and the exact condition that selects each. An agent can route without opening any schema.

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

All TeamPredict HR Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?