GadgetHumans API Hub

by io.github.scotia1973-bot

convert_timestamp

Convert Unix timestamp to date or vice versa

Input Schema

Name	Required	Description	Default
`value`	No	Unix timestamp or date string
`format`	No	iso (default), unix, rfc2822

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 10, 2026

removedInput schema / properties / format / default
```
Removed value: -"iso"
```
addedInput schema / properties / format / description
```
Added value: +"iso (default), unix, rfc2822"
```
removedInput schema / properties / format / title
```
Removed value: -"Format"
```
addedInput schema / properties / value / description
```
Added value: +"Unix timestamp or date string"
```
removedInput schema / properties / value / title
```
Removed value: -"Value"
```
removedInput schema / required
```
Removed value: -[
-  "value"
-]
```

removedInput schema / title

Removed value: -"convert_timestampArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "convert_timestampOutput",
-  "type": "object"
-}New value: +null

First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about how the conversion direction is determined (auto-detect vs. explicit), whether timezones are assumed (e.g., UTC), or what the output looks like. These are meaningful gaps for a conversion tool.

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?

A single efficient sentence, front-loaded with the verb and resource. It is tight, though the brevity comes at the cost of specification rather than from ruthless editing.

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

Completeness2/5

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

No annotations and no output schema, so the description must explain behavior and results, but it omits direction-detection logic, timezone assumptions, and return format. For a conversion tool with real ambiguity against convert_timezone, this is under-specified.

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?

Schema description coverage is 100%, so both parameters are already documented (value as timestamp/date string, format with iso/unix/rfc2822). The description adds only the notion of direction, not any syntax or format detail beyond the schema.

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 states a clear verb and resource ("Convert Unix timestamp to date or vice versa") and even covers bidirectionality. However, it does not distinguish itself from the sibling convert_timezone, which an agent could easily confuse with this tool.

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

Usage Guidelines2/5

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

No guidance on when to use this versus convert_timezone or convert_number_base, no stated prerequisites, and no exclusions. The agent must infer the appropriate context entirely.

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

All GadgetHumans API Hub 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?