Skip to main content
Glama
paladini

devutils-mcp-server

date_to_timestamp

Convert date strings to Unix timestamps for programming and data processing. Supports ISO 8601 and common date formats like '2024-01-15T10:30:00Z' or 'January 15, 2024'.

Instructions

Convert a date string to a Unix timestamp. Accepts ISO 8601 and common date formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate string (e.g., '2024-01-15T10:30:00Z', '2024-01-15', 'January 15, 2024')

Implementation Reference

  • The handler implementation for date_to_timestamp that parses a date and returns Unix timestamps and ISO string.
    async ({ date }) => {
      const parsed = new Date(date);
      if (isNaN(parsed.getTime())) {
        return {
          content: [
            {
              type: "text" as const,
              text: "Error: Could not parse date string. Try ISO 8601 format: 'YYYY-MM-DDTHH:mm:ssZ'.",
            },
          ],
          isError: true,
        };
      }
    
      const result = {
        unix_seconds: Math.floor(parsed.getTime() / 1000),
        unix_milliseconds: parsed.getTime(),
        iso: parsed.toISOString(),
      };
    
      return {
        content: [
          { type: "text" as const, text: JSON.stringify(result, null, 2) },
        ],
      };
    }
  • The registration of the date_to_timestamp tool in the MCP server.
    // Date to Unix timestamp
    server.tool(
      "date_to_timestamp",
      "Convert a date string to a Unix timestamp. Accepts ISO 8601 and common date formats.",
      {
        date: z
          .string()
          .describe(
            "Date string (e.g., '2024-01-15T10:30:00Z', '2024-01-15', 'January 15, 2024')"
          ),
      },
      async ({ date }) => {
        const parsed = new Date(date);
        if (isNaN(parsed.getTime())) {
          return {
            content: [
              {
                type: "text" as const,
                text: "Error: Could not parse date string. Try ISO 8601 format: 'YYYY-MM-DDTHH:mm:ssZ'.",
              },
            ],
            isError: true,
          };
        }
    
        const result = {
          unix_seconds: Math.floor(parsed.getTime() / 1000),
          unix_milliseconds: parsed.getTime(),
          iso: parsed.toISOString(),
        };
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(result, null, 2) },
          ],
        };
      }
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses input format flexibility (ISO 8601 + common formats) but omits critical behavioral details: output precision (seconds vs milliseconds), timezone handling assumptions (UTC vs local), and error handling for malformed dates.

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 captures purpose, second captures input behavior. Zero redundancy, front-loaded, every sentence earns its place.

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

Completeness3/5

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

Adequate for a single-parameter conversion utility, but incomplete regarding output specifications (timezone assumptions, epoch unit) and error states. Given the simplicity and lack of output schema, it covers the minimum but leaves operational ambiguities.

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?

With 100% schema coverage (parameter 'date' fully documented with examples), baseline is 3. Description adds value by categorizing accepted formats ('ISO 8601 and common date formats'), providing semantic grouping beyond the schema's raw examples.

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?

Clear verb+resource ('Convert a date string to a Unix timestamp') and specifies accepted input formats. Lacks explicit differentiation from sibling tool 'timestamp_to_date' (the inverse operation), though the name makes directionality somewhat clear.

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?

Provides input format guidance ('Accepts ISO 8601 and common date formats') but lacks explicit when-to-use guidance, when-not-to-use, or mention of the reverse conversion tool (timestamp_to_date) as an alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paladini/devutils-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server