Skip to main content
Glama

get_current_datetime

Retrieve current date and time in multiple formats for timestamping architectural decision records and research documents. Supports ISO 8601, human-readable, and ADR-specific formats with timezone options.

Instructions

Get the current date and time in various formats. Useful for timestamping ADRs, research documents, and other architectural artifacts. Returns ISO 8601, human-readable, and ADR-specific date formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNoTimezone for the datetime (e.g., "UTC", "America/New_York", "Europe/London"). Defaults to UTC.UTC
formatNoOutput format: "iso" for ISO 8601, "human" for human-readable, "adr" for ADR date format (YYYY-MM-DD), "all" for all formatsall
includeTimestampNoInclude Unix timestamp in milliseconds

Implementation Reference

  • Registration of the 'get_current_datetime' tool in the central TOOL_CATALOG Map, including metadata, category ('utility'), complexity ('simple'), input schema, and indication that it requires no AI execution (requiresAI: false). This is the primary definition and registration point for the tool.
    TOOL_CATALOG.set('get_current_datetime', {
      name: 'get_current_datetime',
      shortDescription: 'Get current date/time',
      fullDescription: 'Gets the current date and time in various formats.',
      category: 'utility',
      complexity: 'simple',
      tokenCost: { min: 50, max: 100 },
      hasCEMCPDirective: true, // Phase 4.3: Simple tool - datetime retrieval
      relatedTools: [],
      keywords: ['datetime', 'time', 'date', 'current'],
      requiresAI: false,
      inputSchema: {
        type: 'object',
        properties: {
          format: { type: 'string', enum: ['iso', 'human', 'adr', 'all'] },
          timezone: { type: 'string' },
        },
      },
    });
  • Input schema definition for the get_current_datetime tool: accepts optional 'format' (iso, human, adr, all) and 'timezone' parameters.
    TOOL_CATALOG.set('get_current_datetime', {
      name: 'get_current_datetime',
      shortDescription: 'Get current date/time',
      fullDescription: 'Gets the current date and time in various formats.',
      category: 'utility',
      complexity: 'simple',
      tokenCost: { min: 50, max: 100 },
      hasCEMCPDirective: true, // Phase 4.3: Simple tool - datetime retrieval
      relatedTools: [],
      keywords: ['datetime', 'time', 'date', 'current'],
      requiresAI: false,
      inputSchema: {
        type: 'object',
        properties: {
          format: { type: 'string', enum: ['iso', 'human', 'adr', 'all'] },
          timezone: { type: 'string' },
        },
      },
    });
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool returns (multiple date formats) and hints at its read-only nature by implying data retrieval, but it does not detail error handling, rate limits, or authentication requirements. The description adds some value but lacks comprehensive behavioral context.

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 appropriately sized and front-loaded, with the core purpose stated first ('Get the current date and time in various formats'), followed by usage context and return details. Every sentence adds value without redundancy, making it efficient and well-structured.

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?

Given the tool's low complexity (no output schema, no annotations, simple parameters), the description is mostly complete for its purpose. It covers what the tool does, when to use it, and what it returns. However, without annotations or output schema, it could benefit from more details on behavioral aspects like error cases or performance.

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?

The schema description coverage is 100%, so the input schema already fully documents all parameters (timezone, format, includeTimestamp). The description mentions 'various formats' and specific use cases like ADRs, which adds minimal semantic context beyond the schema. This meets the baseline for high schema coverage.

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 purpose with specific verbs ('Get') and resources ('current date and time'), and distinguishes it from sibling tools by focusing on datetime retrieval rather than analysis, validation, or file operations. It explicitly mentions the return formats, making the purpose distinct and well-defined.

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?

The description provides clear context for when to use the tool ('Useful for timestamping ADRs, research documents, and other architectural artifacts'), which helps guide its application. However, it does not explicitly state when not to use it or name alternatives among sibling tools, such as for historical date analysis or other time-related operations.

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/tosin2013/mcp-adr-analysis-server'

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