Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Unix timestamp converter: convert a Unix timestamp to a date and time, or a date to a timestamp

unix
Read-only

Convert a Unix timestamp (seconds or milliseconds, detected automatically) to ISO date and time, or an ISO date to a Unix timestamp. Without input, returns the current time in both forms. Use to read timestamps in logs and APIs. Example: value=1792281600. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "unix"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNoUnix seconds/milliseconds or an ISO date (default now)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: automatic seconds-vs-milliseconds detection, the no-input default, and the billing model ($0.01/call, first 25 free, failed calls free, repeats not free) — the last point matters because idempotentHint=false plus per-call charging means repeat calls cost money.

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?

The purpose is front-loaded in the first sentence, followed by default behavior, usage context, an example, and billing. The final billing clause is somewhat dense and merges pricing with the read-only reassurance, but no sentence is wasted.

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?

For a one-parameter converter with no output schema, the description covers accepted input forms, auto-detection, the default-now case, both return shapes, and cost per call. An agent has everything needed to invoke it correctly; only the exact response field names are left implicit.

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 coverage is 100% and the single parameter already documents 'Unix seconds/milliseconds or an ISO date (default now)'. The description only adds a worked example (value=1792281600) and restates auto-detection, which is marginal value beyond the schema; baseline 3 is appropriate.

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 verb and resource — convert a Unix timestamp to ISO date and time, or an ISO date to a timestamp — and names both directions of conversion. It is clearly distinguishable from siblings like date_diff, date_info, and units_convert because it is explicitly about epoch/ISO translation.

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

Usage Guidelines4/5

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

"Use to read timestamps in logs and APIs" gives a concrete usage context, and the no-input default (returns current time in both forms) tells the agent how to call it for a 'now' query. It does not name alternatives or exclusions, but the single-purpose nature of the tool makes that less necessary.

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.