Skip to main content
Glama
armorwallet
by armorwallet

get_current_time

Retrieve the current time and date for synchronization or timestamping tasks within the Armor Crypto MCP server, ensuring accurate blockchain operations and AI agent coordination.

Instructions

Gets the current time and date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_current_time' tool, decorated with @mcp.tool() for registration. It returns the current UTC time as a formatted string in a dictionary.
    @mcp.tool()
    async def get_current_time() -> Dict:
        """Gets the current time and date"""
        return {"current_time": datetime.now(timezone.utc).strftime("%Y-%m-%d %H:%M:%S")}
  • Import statement providing datetime and timezone utilities used by the get_current_time handler.
    from datetime import datetime, timezone
  • The @mcp.tool() decorator registers the get_current_time function as an MCP tool.
    @mcp.tool()
Behavior2/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 'Gets' implying a read operation, but doesn't disclose any behavioral traits such as rate limits, timezone handling, or output format. This is inadequate for a tool with no annotation coverage.

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 no wasted words, front-loading the core purpose. It's appropriately sized for a simple tool, making it easy to parse quickly.

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 (0 params, output schema exists), the description is minimally adequate but lacks depth. It doesn't explain what 'current time and date' entails (e.g., format, timezone), leaving gaps despite the output schema covering return values.

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 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description doesn't add param details, but that's fine here, earning a baseline 4 for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with the verb 'Gets' and the resource 'current time and date', making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools, which are mostly unrelated (e.g., crypto trading, wallet management), so it doesn't fully earn a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. While siblings are unrelated, there's no mention of context, prerequisites, or exclusions, leaving usage unclear beyond the basic purpose.

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

Related 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/armorwallet/armor-crypto-mcp'

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