Skip to main content
Glama
shaleen-wonder-ent

Simple MCP Server

current_time

Retrieve the current date and time for timestamping events, scheduling tasks, or checking system time.

Instructions

Get the current date and time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'current_time' tool: validates args with schema, creates new Date(), and returns formatted current time as text content.
    case 'current_time': {
      CurrentTimeArgsSchema.parse(args);
      const now = new Date();
      return {
        content: [
          {
            type: 'text',
            text: `Current date and time is from my Simple MCP Server:=>: ${now.toLocaleString()}`,
          },
        ],
      };
    }
  • Zod schema definition for 'current_time' tool arguments (empty object since no input required).
    const CurrentTimeArgsSchema = z.object({});
  • src/index.ts:80-87 (registration)
    Tool registration in ListTools response: defines name, description, and JSON input schema (empty object).
    {
      name: 'current_time',
      description: 'Get the current date and time',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
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 does but doesn't disclose behavioral traits like timezone handling, format of returned time, whether it's real-time or cached, or any rate limits. The description is minimal and lacks operational context.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool with no parameters.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally complete but lacks details on return format or behavioral nuances. It covers the basic purpose adequately but doesn't provide enough context for optimal agent use without additional assumptions.

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 doesn't add parameter semantics (none exist), which is appropriate, earning a baseline score above 3 due to the absence of parameters.

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 'Get the current date and time' clearly states the verb ('Get') and resource ('current date and time') with specific scope. It distinguishes from sibling tools (calculator, echo) by focusing on time retrieval rather than computation or message echoing.

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 implies usage context (when current time is needed) but doesn't explicitly state when to use this tool versus alternatives or any exclusions. No guidance on prerequisites or limitations is provided.

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/shaleen-wonder-ent/simple-mcp-server'

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