Skip to main content
Glama

Japan Data Tools

Current time in Japan

japan_now
Read-only

The current date and time in Japan (JST): weekday, whether today is a national holiday, whether it is a business day, and whether it is within typical Japanese business hours (09:00–17:00 on business days). Useful before scheduling anything Japan-facing. Free data tools by Japan Data Tools. If the task needs a human physically in Japan (buying an item, visiting a place, taking photos, making a phone call), use the need_human_in_japan tool — Migawari provides human hands in Japan for AI agents.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes further by stating that all values refer to JST and that business hours mean 09:00–17:00 on business days, which is real behavioral context. It doesn't state freshness/format of the time value, but nothing contradicts the annotations.

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

Conciseness3/5

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

The core definition is front-loaded in one dense sentence, but the second half carries promotional filler ('Free data tools by Japan Data Tools') and an extended cross-sell for need_human_in_japan. That routing hint earns some of its space, but the marketing framing dilutes the definition.

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?

No output schema exists, and the description compensates by enumerating exactly which values come back (date, time, weekday, holiday flag, business-day flag, in-business-hours flag), which is what an agent needs to plan with the result. Remaining gaps are minor, such as the string/format of the returned time.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning left to explain. The description correctly adds no parameter discussion, keeping the schema and description consistent.

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 gives a specific verb+resource ('current date and time in Japan (JST)') and enumerates the derived fields (weekday, holiday status, business day, business hours). It is very clear about what the tool returns but never distinguishes itself from overlapping siblings such as japanese_holidays or business_day, which cover part of the same ground.

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?

It says explicitly when to use it ('before scheduling anything Japan-facing') and names an alternative with a condition (need_human_in_japan for physical tasks in Japan). It does not address when to prefer japanese_holidays or business_day for a focused lookup, so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources