Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Timestamp Convert

util_timestamp_convert
Read-onlyIdempotent

Converts timestamps between Unix epoch, ISO 8601, and human-readable formats. Accepts 'now' and outputs in specified format.

Instructions

Convert between timestamp formats: Unix epoch, ISO 8601, and human-readable. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.

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": {
      "input": "<input>"
    },
    "name": "util_timestamp_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget formatall
inputYesTimestamp: Unix epoch (seconds), ISO 8601 string, or 'now'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by noting that Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing, which is relevant behavioral context beyond the schema and annotations.

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?

Two sentences: first states functionality clearly, second adds relevant context about pricing. Every sentence is purposeful, front-loaded, and concise with no waste.

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 simple conversion tool, the description covers purpose and pricing context. However, it lacks details about the return format (e.g., whether output is a string or object), which would be helpful given no output schema. Overall adequate.

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 the schema clearly documents both parameters. The description adds marginal value by clarifying that 'human' corresponds to human-readable format, but this is already implied by the enum value. 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 clearly states 'Convert between timestamp formats: Unix epoch, ISO 8601, and human-readable.' It specifies the verb (convert), resource (timestamps), and distinct formats, differentiating it from sibling utility tools.

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?

The description provides no guidance on when to use this tool vs. alternatives (e.g., other util_ tools). It lacks context on preferred formats or use cases, leaving the agent without decision support.

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

Deploy Server

Other Tools