Skip to main content
Glama
enesjakozh
webdevtodayjason

Slim MCP

by webdevtodayjason
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_current_utc_time

Retrieve the current UTC date and time for synchronization, scheduling, or timestamping needs in automated workflows and AI agent integrations.

Instructions

Get the current UTC date and time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/claude_tools/datetime_tool.py:9-13 (handler)
    The handler function that implements the logic for the 'get_current_utc_time' tool, fetching and formatting the current UTC datetime.
    def get_current_utc_time() -> str:
    """Get the current UTC date and time.
    """
    now = datetime.now(timezone.utc)
    return f"Current UTC date and time: {now.strftime('%Y-%m-%d %H:%M:%S UTC')}"
  • src/claude_tools/datetime_tool.py:18-18 (registration)
    The registration of the 'get_current_utc_time' tool using the mcp.tool() decorator within the register_datetime_tools function.
    mcp.tool()(get_current_utc_time)
  • src/claude_tools/main.py:26-26 (registration)
    Invocation of the register_datetime_tools function in the main entry point, which triggers the tool registration.
    register_datetime_tools(mcp)

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool returns the current UTC date and time, which is clear but lacks details like format, precision, or whether it's real-time versus cached. It doesn't disclose behavioral traits such as rate limits or authentication needs, though these may be less critical for a simple time-fetching tool.

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 that front-loads the essential information ('Get the current UTC date and time') with zero wasted words. It is 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.

Completeness4/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, simple purpose) and the presence of an output schema (which handles return values), the description is complete enough. It clearly states what the tool does, though it could benefit from slight elaboration on usage context or output format to reach a perfect score.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter information, focusing on the tool's purpose. A baseline of 4 is applied as it compensates adequately for the lack 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 clearly states the specific action ('Get') and resource ('current UTC date and time'), distinguishing it from sibling tools like 'get_current_time' (which might return local time) and 'calculate' (which performs computations). It precisely defines what the tool does without ambiguity.

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 for obtaining UTC time, but does not explicitly state when to use this tool versus alternatives like 'get_current_time' or other time-related tools. No guidance is provided on exclusions or prerequisites, leaving usage context to inference.

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/webdevtodayjason/slim-MCP'

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