Skip to main content
Glama
Sign In
TypeScript MCP Server Boilerplate

TypeScript MCP Server Boilerplate

by kimhailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

time

Returns the current date and time, optionally specifying a timezone such as Asia/Seoul or UTC.

Instructions

현재 날짜와 시간을 반환합니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNo타임존 (기본값: Asia/Seoul, 예: America/New_York, UTC)Asia/Seoul

Output Schema

NameRequiredDescriptionDefault
contentYes현재 시간 정보

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral details. It only states the basic return value without specifying format, timezone handling beyond parameter, or any side effects. This leaves important behavioral aspects undisclosed.

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 immediately conveys the tool's purpose. Every word is necessary, and there is no redundant or extraneous information.

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 simplicity and the existence of an output schema, the description is minimally adequate. However, it lacks details about return format or example usage, which would enhance completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of the single parameter with a description of timezone. The tool description does not add further semantic value beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 the tool returns the current date and time, using a specific verb and resource. It is easily distinguishable from sibling tools like calculate or weather, which cover different domains.

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 explicitly state when to use or avoid this tool. However, the purpose is straightforward and implied for any situation needing the current date/time, so it is adequate but lacks explicit guidance or alternatives.

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