Skip to main content
Glama
t-shiratori

Time Tools MCP Server

get_unixtime

Retrieve the current Unix timestamp for time-sensitive operations, data logging, or system synchronization.

Instructions

Get unixtime (e.g. 1746627290)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler for the 'get_unixtime' tool. Computes the current Unix timestamp using dayjs().unix() and returns it as a text content block. This is also the registration point via server.tool.
    server.tool("get_unixtime", "Get unixtime (e.g. 1746627290)", async () => {
        const unixTimestamp = dayjs().unix();
        return {
            content: [
                {
                    type: "text",
                    text: String(unixTimestamp),
                },
            ],
        };
    });
  • src/index.ts:35-45 (registration)
    Registration of the 'get_unixtime' tool using server.tool, with description and inline handler function.
    server.tool("get_unixtime", "Get unixtime (e.g. 1746627290)", async () => {
        const unixTimestamp = dayjs().unix();
        return {
            content: [
                {
                    type: "text",
                    text: String(unixTimestamp),
                },
            ],
        };
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool returns ('unixtime') but doesn't disclose behavioral traits like whether it returns current system time, requires network access, has rate limits, or provides timezone context. The example suggests it returns a numeric timestamp, but that's implied by 'unixtime' itself.

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 extremely concise (one short sentence with a helpful example) and front-loaded with the core purpose. Every word earns its place—'Get' establishes the action, 'unixtime' specifies the resource, and the example clarifies the format without redundancy.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It tells the agent what the tool returns but lacks context about time source, precision, or differences from sibling tools. For a basic time-fetching tool, this might suffice, but gaps remain in behavioral transparency.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the output. This meets the baseline of 4 for zero-parameter tools.

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 resource ('unixtime'), providing a concrete example (1746627290) that illustrates the output format. However, it doesn't differentiate from siblings like 'get_current_date_time' or 'convert_datetime_to_unix', which might return similar time-related data in different formats.

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 versus alternatives. With siblings like 'get_current_date_time' (which might return human-readable time) and conversion tools, the agent has no indication whether this tool is for current time, a specific time, or general Unix time retrieval.

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/t-shiratori/time-tools-mcp-server'

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