Skip to main content
Glama
Jake-loranger

Algorand MCP Server

get_current_time

Retrieve the current time for any specified timezone to synchronize blockchain operations with local or global time requirements.

Instructions

Get the current time in a specified timezone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNoTimezone identifier (e.g., "UTC", "America/New_York")

Implementation Reference

  • Handler for the 'get_current_time' tool: parses optional timezone argument, formats current date using toLocaleString, handles invalid timezones with error response.
    case 'get_current_time': {
        const parsed = GetTimeArgsSchema.parse(args);
        const timezone = parsed.timezone || 'UTC';
    
        try {
            const now = new Date();
            const timeString = now.toLocaleString('en-US', {
                timeZone: timezone,
                weekday: 'long',
                year: 'numeric',
                month: 'long',
                day: 'numeric',
                hour: '2-digit',
                minute: '2-digit',
                second: '2-digit',
                timeZoneName: 'short',
            });
    
            return {
                content: [
                    {
                        type: 'text',
                        text: `Current time in ${timezone}: ${timeString}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error: Invalid timezone "${timezone}" - ${error}`,
                    },
                ],
                isError: true,
            };
        }
    }
  • Zod schema used for input validation in the get_current_time handler: optional 'timezone' string.
    const GetTimeArgsSchema = z.object({
        timezone: z.string().optional(),
    });
  • src/index.ts:128-141 (registration)
    Tool registration in TOOLS array: defines name, description, and input schema for MCP listTools response.
    {
        name: 'get_current_time',
        description: 'Get the current time in a specified timezone',
        inputSchema: {
            type: 'object',
            properties: {
                timezone: {
                    type: 'string',
                    description: 'Timezone identifier (e.g., "UTC", "America/New_York")',
                },
            },
            required: [],
        },
    },
  • MCP protocol input schema for get_current_time tool as registered in TOOLS.
    inputSchema: {
        type: 'object',
        properties: {
            timezone: {
                type: 'string',
                description: 'Timezone identifier (e.g., "UTC", "America/New_York")',
            },
        },
        required: [],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It lacks details on permissions, rate limits, error handling, or return format (e.g., timestamp structure). This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It is front-loaded with the core purpose and appropriately sized for a simple tool.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple but undocumented behavioral profile, the description is incomplete. It doesn't explain what 'current time' means (e.g., server time, formatted string), error cases for invalid timezones, or return values, leaving gaps for agent usage.

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 fully documents the optional 'timezone' parameter. The description adds no additional meaning beyond implying timezone specification, matching the baseline for high schema coverage without extra param context.

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?

The description clearly states the verb 'Get' and the resource 'current time', specifying the action and target. It distinguishes from siblings by focusing on time retrieval rather than financial or asset operations, though it doesn't explicitly name alternatives for time-related functions.

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

Usage Guidelines3/5

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

The description implies usage when current time in a specific timezone is needed, but provides no explicit guidance on when to use this tool versus alternatives (e.g., system time functions or other time tools). No exclusions or prerequisites are mentioned.

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/Jake-loranger/algorand-mcp-server'

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