Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

get_current_time

Obtain the current date and time in ISO 8601 format. Use it to add accurate timestamps to logs, synchronize actions, or record events with precise temporal data.

Instructions

Return the current date and time in ISO 8601 format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_current_time tool is registered as an MCP tool via the @mcp.tool() decorator inside the register() function. The registration function is called from tools/__init__.py.
    def register(mcp, *, config) -> None:
        @mcp.tool()
        def get_current_time() -> str:
            """Return the current date and time in ISO 8601 format."""
            return datetime.datetime.now(datetime.UTC).isoformat()
  • The actual handler function for get_current_time: returns the current date and time in ISO 8601 format using datetime.datetime.now(datetime.UTC).isoformat().
    @mcp.tool()
    def get_current_time() -> str:
        """Return the current date and time in ISO 8601 format."""
        return datetime.datetime.now(datetime.UTC).isoformat()
  • The register_all_tools function calls system.register(mcp, config=config) which triggers the registration of get_current_time.
    def register_all_tools(mcp, *, config, skill_store) -> None:
        system.register(mcp, config=config)
Behavior3/5

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

The description states the output format (ISO 8601) but does not specify timezone behavior (e.g., UTC vs local). Given no annotations, transparency could be improved by clarifying timezone.

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 sentence that conveys the essential function without any unnecessary words. It is optimally concise.

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 zero parameters and an output schema that likely defines the return type, the description sufficiently covers the tool's purpose and output format. No additional context is needed.

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 no parameters, so the description is not required to add parameter semantics. Baseline of 4 is appropriate as it avoids irrelevant detail.

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 explicitly states it returns the current date and time in ISO 8601 format, which is a clear and specific action. It distinguishes itself from sibling tools, none of which provide time retrieval.

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 clearly indicates when to use the tool (to get current time). While it does not mention when not to use it or provide alternatives, the tool's simplicity makes such guidance unnecessary.

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/JeremyLakeyJr/mcp-server'

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