Skip to main content
Glama
Sign In
my-mcp-server

my-mcp-server

by KALYN100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-time

Retrieve current date and time for any IANA timezone. Input a timezone string to get the local time.

Instructions

IANA 타임존을 입력하면 해당 지역의 현재 날짜와 시간을 반환합니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timezone": "<timezone>"
    },
    "name": "get-time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneYes도시가 속한 IANA 타임존 (예: Asia/Seoul, America/New_York)

Output Schema

NameRequiredDescriptionDefault
timezoneYes입력한 IANA 타임존
currentTimeYes해당 타임존의 현재 날짜와 시간

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

The description discloses the input (IANA timezone) and output (current date and time) beyond the schema. While no annotations exist, the behavior is simple and adequately explained.

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, concise sentence that front-loads the purpose. Every word is necessary.

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

Completeness4/5

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

Given the presence of an output schema, the description is mostly complete. It could mention error handling for invalid timezones, but otherwise adequate.

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?

Schema coverage is 100% with a basic description. The description adds value by specifying the IANA format and providing examples, which clarifies parameter semantics.

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 clearly states that the tool returns the current date and time for an IANA timezone, effectively distinguishing it from siblings like get-weather and geocode.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get-weather might also involve time). The description does not mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools