Skip to main content
Glama

get_current_time

Retrieve the current local date and time formatted as YYYY-MM-DD HH:MM:SS for timestamping or scheduling purposes within the MUSTer campus system.

Instructions

Get current local datetime as YYYY-MM-DD HH:MM:SS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:185-188 (handler)
    Handler function that executes the tool logic: returns the current local datetime formatted as YYYY-MM-DD HH:MM:SS.
    def tool_get_current_time() -> str:
        current_time = datetime.now()
        return current_time.strftime("%Y-%m-%d %H:%M:%S")
  • main.py:82-86 (schema)
    Tool schema definition: name, description, and empty input schema (no parameters required).
    Tool(
        name="get_current_time",
        description="Get current local datetime as YYYY-MM-DD HH:MM:SS.",
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
  • main.py:217-218 (registration)
    Tool dispatch/registration in the call_tool handler: checks name and calls the tool_get_current_time function.
    if name == "get_current_time":
        return _wrap_json(tool_get_current_time())
Behavior3/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 discloses the return format but lacks behavioral details like timezone handling, freshness guarantees, or error conditions. The description is accurate but minimal for behavioral 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 front-loads the core purpose and includes essential format details, making it optimally concise and well-structured for its simplicity.

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, no annotations, no output schema), the description is nearly complete. It covers purpose and output format adequately, though minor gaps in behavioral details prevent 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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description appropriately omits parameter details since none exist, focusing instead on the output format, which adds value beyond the empty schema.

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 verb ('Get') and resource ('current local datetime'), with precise format details ('YYYY-MM-DD HH:MM:SS'). It distinguishes itself from siblings by focusing solely on time retrieval rather than courses, schedules, or resources.

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 when current datetime is needed, but provides no explicit guidance on when to use this versus alternatives or exclusions. No sibling tools offer similar time functionality, so differentiation isn't critical, but general context is missing.

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/Cosmostima/MUSTer_MCP'

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