Skip to main content
Glama
kongyo2

EVE Online EST MCP Server

getCurrentESTTime

Read-only

Retrieve current EVE Online server time (EST/UTC) and calculate time remaining until the next daily downtime, which occurs from 11:00 to 11:15 EST. Uses system time with WorldTimeAPI as a fallback.

Instructions

Get current EVE Server Time (EST) which is identical to UTC, and calculate time until next server downtime. EVE Online servers go offline daily from 11:00 to 11:15 EST (UTC) for maintenance. Uses system time with WorldTimeAPI as fallback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler (execute function) for 'getCurrentESTTime'. It calls the core helper function and returns the result as formatted JSON, with error handling.
    execute: async () => {
      try {
        const timeInfo = await getCurrentESTTime();
        return JSON.stringify(timeInfo, null, 2);
      } catch (error) {
        const errorMessage =
          error instanceof Error ? error.message : String(error);
        return JSON.stringify(
          {
            error: "Failed to get current time",
            message: errorMessage,
            timestamp: new Date().toISOString(),
          },
          null,
          2,
        );
      }
    },
  • Zod schema defining the tool's input parameters: an empty object (no parameters required).
    parameters: z.object({}),
  • src/server.ts:99-127 (registration)
    FastMCP tool registration for 'getCurrentESTTime', including annotations, description, handler (execute), name, and parameters schema.
    server.addTool({
      annotations: {
        openWorldHint: true, // May use external API as fallback
        readOnlyHint: true, // This tool doesn't modify anything
        title: "Get Current EVE Server Time",
      },
      description:
        "Get current EVE Server Time (EST) which is identical to UTC, and calculate time until next server downtime. EVE Online servers go offline daily from 11:00 to 11:15 EST (UTC) for maintenance. Uses system time with WorldTimeAPI as fallback.",
      execute: async () => {
        try {
          const timeInfo = await getCurrentESTTime();
          return JSON.stringify(timeInfo, null, 2);
        } catch (error) {
          const errorMessage =
            error instanceof Error ? error.message : String(error);
          return JSON.stringify(
            {
              error: "Failed to get current time",
              message: errorMessage,
              timestamp: new Date().toISOString(),
            },
            null,
            2,
          );
        }
      },
      name: "getCurrentESTTime",
      parameters: z.object({}),
    });
  • Core helper function that implements the logic for getting current EVE Server Time (EST/UTC), calculating time until next downtime, checking if currently in downtime, with time source info.
    async function getCurrentESTTime() {
      const { source: timeSource, time: now } = await getCurrentTime();
    
      // EVE Server Time is UTC
      const estTime = now.toISOString().replace("T", " ").substring(0, 19) + " EST";
    
      // Calculate time until next downtime (11:00 UTC)
      const downtimeHour = 11;
      const downtimeMinute = 0;
    
      // Create downtime date for today
      const nextDowntime = new Date(now);
      nextDowntime.setUTCHours(downtimeHour, downtimeMinute, 0, 0);
    
      // If current time is past today's downtime, set to tomorrow's downtime
      if (now >= nextDowntime) {
        nextDowntime.setUTCDate(nextDowntime.getUTCDate() + 1);
      }
    
      // Calculate time difference
      const timeDiff = nextDowntime.getTime() - now.getTime();
      const hoursUntilDowntime = Math.floor(timeDiff / (1000 * 60 * 60));
      const minutesUntilDowntime = Math.floor(
        (timeDiff % (1000 * 60 * 60)) / (1000 * 60),
      );
    
      // Check if server is currently in downtime (11:00-11:15 UTC)
      const currentHour = now.getUTCHours();
      const currentMinute = now.getUTCMinutes();
      const isInDowntime = currentHour === 11 && currentMinute < 15;
    
      return {
        currentTime: estTime,
        downtimeWindow: "11:00 to 11:15 EST (UTC)",
        isInDowntime,
        nextDowntimeStart:
          nextDowntime.toISOString().replace("T", " ").substring(0, 19) + " EST",
        timeSource,
        timeUntilNextDowntime: isInDowntime
          ? "Server is currently in downtime"
          : `${hoursUntilDowntime}h ${minutesUntilDowntime}m`,
        utcTime: now.toISOString(),
      };
    }
  • Helper function to retrieve current time, preferring system clock but falling back to WorldTimeAPI if invalid.
    async function getCurrentTime(): Promise<{ source: string; time: Date }> {
      try {
        const now = new Date();
        // Check if system time is valid (not NaN and reasonable)
        if (isNaN(now.getTime()) || now.getFullYear() < 2020) {
          throw new Error("System time appears invalid");
        }
        return { source: "system", time: now };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        console.warn(
          "System time unavailable, falling back to WorldTimeAPI:",
          errorMessage,
        );
        const apiTime = await fetchTimeFromAPI();
        return { source: "worldtimeapi", time: apiTime };
      }
    }
Behavior4/5

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

The description adds valuable behavioral context beyond what annotations provide. While annotations indicate read-only and open-world operations, the description reveals specific implementation details: the tool uses system time with WorldTimeAPI as fallback, and it calculates time until the next scheduled downtime. This provides practical information about reliability and functionality that annotations don't cover.

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 perfectly concise and well-structured. It uses just two sentences that each earn their place: the first states the primary function, the second provides important operational context about daily maintenance and implementation details. There's zero wasted language or redundancy.

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 parameterless tool with good annotations (readOnlyHint, openWorldHint) but no output schema, the description provides excellent context about what the tool returns (current time and downtime calculation) and how it works (system time with API fallback). The only minor gap is not explicitly describing the output format, but given the tool's simplicity and clear purpose, this is acceptable.

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 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does with no inputs. This is efficient and correct for a parameterless tool.

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 current EVE Server Time' and 'calculate time until next server downtime') and identifies the resource (EVE Online servers). It distinguishes this as a time-checking tool with maintenance scheduling functionality, which is unambiguous even without sibling tools.

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 about when to use this tool - for checking EVE Online server time and calculating downtime. It mentions the specific daily maintenance window (11:00-11:15 EST/UTC), giving users clear situational guidance. However, with no sibling tools, there's no need for alternative tool guidance, so it can't achieve a perfect 5.

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

Related 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/kongyo2/EVE-EST-MCP'

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