Skip to main content
Glama

timestamp

Retrieve the current UTC timestamp to synchronize time-sensitive operations in your applications.

Instructions

Get the current UTC timestamp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'timestamp' tool logic. It takes no input parameters and returns the current UTC time as an ISO string via new Date().toISOString().
    // Example tool: get current timestamp
    server.tool(
      "timestamp",
      "Get the current UTC timestamp",
      {},
      async () => ({
        content: [{ type: "text", text: new Date().toISOString() }],
      })
    );
  • Input schema for the 'timestamp' tool - an empty object `{}`, meaning the tool takes no parameters.
    {},
  • src/index.ts:21-28 (registration)
    Registration of the 'timestamp' tool via server.tool() with name 'timestamp', description 'Get the current UTC timestamp', empty input schema, and the handler function.
    server.tool(
      "timestamp",
      "Get the current UTC timestamp",
      {},
      async () => ({
        content: [{ type: "text", text: new Date().toISOString() }],
      })
    );
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It clearly indicates a read-only operation returning a timestamp, but lacks details on format (e.g., seconds vs. milliseconds) or any potential edge cases, though the simplicity of the tool makes this minor.

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, front-loaded sentence with zero extraneous words. It efficiently communicates the tool's purpose for a parameterless tool.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema, no complex behavior), the description fully suffices. It answers the fundamental question of what the tool does without omission.

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?

No parameters exist, so baseline is 4. Schema coverage is 100% by default, and the description adds no parameter information because none is needed.

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 precisely states the tool's function: 'Get the current UTC timestamp'. It uses a specific verb ('get') and resource ('current UTC timestamp'), clearly distinguishing it from the unrelated sibling 'echo'.

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 does not provide any guidance on when to use this tool versus alternatives or mention any prerequisites. It implies usage for obtaining the current timestamp, but no explicit context or exclusions are given.

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/shellsage-ai/mcp-server-boilerplate'

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