Skip to main content
Glama

get_current_date

Retrieve the current date and time for email management tasks, such as scheduling messages or timestamping operations within the Mail MCP Server.

Instructions

Get current date and time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_current_date tool within the IMAPClient class.
    def get_current_date(self) -> str:
        """Get current date in ISO format."""
        return datetime.now().isoformat()
  • Tool registration for get_current_date in the MCP tools definition list.
    Tool(
        name="get_current_date",
        description="Get current date and time",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Tool handler logic that calls the IMAPClient.get_current_date method.
    elif name == "get_current_date":
        result = client.get_current_date()
        return [TextContent(type="text", text=str(result))]
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden but only implies read-only safety through the word 'Get'. It fails to specify return format (ISO string, timestamp, object?), timezone handling (UTC vs local), or precision (date only vs datetime).

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?

Extremely concise at four words. Every word is essential; no filler or redundancy. Purpose is immediately stated.

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 zero parameters and no output schema, the description minimally suffices by stating the operation. However, it omits return value format details that would be necessary for an agent to correctly use this value in email filtering or timestamping operations.

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?

Zero parameters exist, establishing a baseline of 4. The description appropriately requires no parameter clarification.

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 uses a specific verb ('Get') and resource ('current date and time'), clearly distinguishing this utility from the email manipulation siblings (copy_email, delete_email, etc.).

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?

No explicit when-to-use guidance is provided, though usage is implied (use when current date/time is needed). Since no sibling tools provide date functionality, differentiation from alternatives is moot, but integration guidance within the email workflow is absent.

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

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