Skip to main content
Glama

Agent Bits

by dev.agentbits

timestamp_convert

Convert Unix epoch seconds or milliseconds to ISO-8601, or an ISO-8601 datetime to Unix epoch values, when bridging APIs that disagree on time formats.

Use when:

  • Convert this Unix timestamp to ISO-8601

  • Turn an ISO-8601 datetime into epoch milliseconds

  • Bridge APIs that mix Unix seconds and ISO-8601 strings

Do not use when:

  • Convert a datetime between IANA timezones while preserving the instant (use timezone_convert)

  • Convert length, mass, or temperature units (use unit_convert)

  • Interpret relative phrases like 'next Tuesday' or 'in 3 hours'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesUnix timestamp or ISO-8601 datetime
input_formatYesFormat of value

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the bidirectional conversion and the API-bridging context, but it does not state what output format is returned (e.g., whether an input of unix_seconds produces an ISO-8601 string) or any error handling/edge cases. This leaves some behavioral ambiguity.

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?

The description is well-structured with a one-sentence summary followed by bullet-point use/not-use cases. Every sentence adds value, and the structure is easy to parse.

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?

Despite lacking an output schema, the description comprehensively covers what the tool does and when to use it. However, it omits details about the return value format and potential precision issues, which would be helpful for a converter. It is still quite complete given its simplicity.

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?

The schema already covers both parameters with descriptions, but the description adds usage context by giving concrete conversion directions ('Unix timestamp to ISO-8601', 'ISO-8601 datetime into epoch milliseconds') that clarify how the parameters are used together. This complements the enum values.

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 clearly states the tool's function: converting between Unix epoch seconds/milliseconds and ISO-8601 datetime. It uses a specific verb 'Convert' and identifies the resource (time formats). It also distinguishes itself from sibling tools like timezone_convert and unit_convert in the 'Do not use when' section.

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?

The description has explicit 'Use when' and 'Do not use when' sections with concrete query examples and alternative tool names (timezone_convert, unit_convert). This gives the agent clear guidance on when to select this tool over its siblings.

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

All Agent Bits toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct data format and operation, with explicit 'Do not use when' cross-references to prevent confusion. For example, base64_encode/decode, url_encode/decode, and timestamp_convert/timezone_convert are clearly separated, and the various validators (ISBN, Luhn, UUID, JSON) apply to different identifiers.

Naming Consistency4/5

Most tool names follow an object_operation pattern (e.g., base64_decode, country_lookup, timestamp_convert), using lowercase with underscores. The main deviation is countries_bulk, which uses a noun+adjective form without an explicit operation, making it inconsistent with the verb-like operations used elsewhere.

Tool Count3/5

With 18 tools, the server falls into the 16-25 range which feels heavy for a utility collection. While each tool is individually useful and the scope is broad, the count is higher than typical for a well-focused server and may overwhelm agents scanning the available options.

Completeness4/5

The set provides solid coverage of encoding/decoding, validation, lookups, and conversions, with paired encode/decode and convert functions. However, some common utilities such as hashing, HTML entity encoding, UUID generation, or email validation are absent, leaving minor gaps for agents that need those operations.

Resources