perseus

perseus_date

Read-only

Need the current date/time in a specific format? Retrieve it with customizable tokens like YYYY, MM, DD, HH, mm, ss, z.

Instructions

Current date/time

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": "perseus_date"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	Date format using tokens YYYY, MM, DD, HH, mm, ss, z (default: YYYY-MM-DD HH:mm:ss). strftime-style %Y %m %d %H %M %S tokens are also accepted.

Output Schema

Name	Required	Description
`unix`	No	Unix epoch seconds
`iso8601`	No	ISO-8601 formatted timestamp
`datetime`	No	Current date/time string

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.14Jul 7, 2026

changedInput schema / properties / format / description

Previous value: -"strftime format string (default: %Y-%m-%d %H:%M:%S)"New value: +"Date format using tokens YYYY, MM, DD, HH, mm, ss, z (default: YYYY-MM-DD HH:mm:ss). strftime-style %Y %m %d %H %M %S tokens are also accepted."

Changed1 schema field changedv1.0.10Jun 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "datetime": {
+      "description": "Current date/time string",
+      "type": "string"
+    },
+    "iso8601": {
+      "description": "ISO-8601 formatted timestamp",
+      "type": "string"
+    },
+    "unix": {
+      "description": "Unix epoch seconds",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv1.0.7Jun 10, 2026

changedInput schema / properties / format / description

Previous value: -"format= modifier for @date"New value: +"strftime format string (default: %Y-%m-%d %H:%M:%S)"

First observedv0.1.0May 27, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotation readOnlyHint=true indicates a safe read operation, and the description adds context by specifying the information returned (current date/time). No contradictions. The description adds value beyond annotations by clarifying the exact output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with one short sentence. It is front-loaded and contains no extraneous information. However, it could be slightly more descriptive (e.g., including 'Returns the current date and time') without losing conciseness.

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?

For a simple read-only tool with a single optional parameter and an output schema present, the description provides sufficient context to understand the tool's basic function. No additional details are necessary for correct invocation given the richness of the schema and annotations.

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?

Schema description coverage is 100%, with the only parameter 'format' having a detailed description. The tool description does not add additional meaning about the parameter 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.

Purpose4/5

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

The description 'Current date/time' clearly indicates the tool returns the current date and time. It is a specific verb+resource (get current date/time), and there are no sibling tools with similar functionality, so differentiation is not needed. A slight improvement would be adding a verb like 'Returns'.

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 does not provide any guidance on when to use this tool versus alternatives. No usage context, prerequisites, or exclusions are mentioned, which is a notable gap even for a simple tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.