codecalc

Overview Schema Source Related Servers Discussions Admin

Human Duration

human_duration

Read-onlyIdempotent

Convert elapsed seconds into a human-readable duration like '2d 3h 4m 5s', plus per-day and per-30-day rates. Use it when you need a clear, concise breakdown of a time span instead of raw seconds.

Instructions

Convert a SPAN of elapsed seconds into a humanised duration (e.g. '2d 3h 4m 5s') plus per-day and per-30d rates. For an epoch timestamp to a calendar date, use epoch_time instead. For byte counts, not seconds, use data_sizes. Returns human, per_day, per_30d, and the echoed seconds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seconds`	Yes	Elapsed span in seconds (not a point-in-time timestamp) to humanize, e.g. into '2d 3h 4m 5s'

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Sep 9, 2026

addedInput schema / properties / seconds / description

Added value: +"Elapsed span in seconds (not a point-in-time timestamp) to humanize, e.g. into '2d 3h 4m 5s'"

Changed1 schema field changedv0.11.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "human_durationDictOutput",
+  "type": "object"
+}

Changed4 schema fields changedv0.2.0Aug 19, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / seconds / title
```
Added value: +"Seconds"
```
- addedInput schema / title
```
Added value: +"human_durationArguments"
```
- changedOutput schema / (root)
```
Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
```
First observedv0.1.0Aug 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description supplements this by naming returned fields (`human`, `per_day`, `per_30d`) and emphasizing that input is an elapsed span, not a point-in-time timestamp. That is useful but not exhaustive behavior detail; annotations carry much of the safety profile.

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?

Four sentences, none redundant; purpose first, sibling routing second/third, return shape last.

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?

Complete enough for a simple conversion tool with one parameter heavily documented in schema den output schema present. Could mention precision/rounding edge cases but these are not essential for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents seconds at 100% coverage Conclusion description about 'elapsed span' reinforces the point-in-time/timestamp distinction but adds no new parameter constraints. Baseline 3 is appropriate because structured coverage handles the parameter.

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?

The description states a specific action: convert an elapsed span of seconds into a human-readable duration plus per-day and per-30d rates. It also explicitly contrasts itself with epoch_time and data_sizes, so an agent can immediately distinguish this tool from siblings.

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?

It gives explicit routing guidance: use epoch_time for timestamps and data_sizes for byte counts. This is clear when-to-use/when-not-to-use information, not just a vague description.

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