Skip to main content
Glama
Sign In
MCP-timeserver

MCP-timeserver

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get-current-time

Retrieve the current time in the configured local timezone to provide accurate datetime information to agentic systems and chat REPLs.

Instructions

Get the current time in the configured local timezone

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": "get-current-time"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosure. It adds the key behavioral detail that time is in the configured local timezone, not UTC or system time. No side effects exist for a read-only clock, so this is adequate.

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, front-loaded sentence with zero wasted words. Every word earns its place, conveying both action and timezone context efficiently.

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?

For a trivial stateless tool with no parameters and no output schema, the description is complete: it states what is retrieved and the timezone context. Nothing more 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 zero parameters, and schema_description_coverage is 100% (empty schema). The baseline for 0 params is 4, and the description adds no unnecessary parameter details, so this score 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 uses a clear verb ('Get') and specific resource ('current time') with a relevant qualifier ('in the configured local timezone'). It unambiguously describes the tool's function, even without sibling differentiation needed.

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?

There are no sibling tools or alternatives, so explicit when-to-use guidance is unnecessary. The description provides clear context (retrieves current time), which is sufficient for this simple tool. Lacks explicit exclusions but none are needed.

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