不動産情報サービス MCP

時刻取得 / Get Current Time

get-time

Read-only

指定したタイムゾーンの現在時刻を取得します。フォーマット文字列には date-fns の形式を使用します（例: 'yyyy-MM-dd HH:mm:ss', 'yyyy年MM月dd日 HH時mm分ss秒'）。24時間表記には 'HH' を使用してください。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`timezone`	No	タイムゾーン (IANA 形式。例: 'Asia/Tokyo'。省略時: Asia/Tokyo)	Asia/Tokyo
`formatStr`	No	フォーマット文字列 (date-fns形式。省略時: 'yyyy-MM-dd HH:mm:ss')	yyyy-MM-dd HH:mm:ss

Output Schema

TableJSON Schema

Name	Required	Description	Default
`time`	Yes	フォーマット済みの現在時刻
`timezone`	Yes	使用したタイムゾーン

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedJul 15, 2026

addedInput schema / properties / formatStr / default
```
Added value: +"yyyy-MM-dd HH:mm:ss"
```

changedInput schema / properties / formatStr / description

Previous value: -"フォーマット文字列 (date-fns形式)"New value: +"フォーマット文字列 (date-fns形式。省略時: 'yyyy-MM-dd HH:mm:ss')"

addedInput schema / properties / timezone / default
```
Added value: +"Asia/Tokyo"
```

changedInput schema / properties / timezone / description

Previous value: -"タイムゾーン (例: 'Asia/Tokyo')"New value: +"タイムゾーン (IANA 形式。例: 'Asia/Tokyo'。省略時: Asia/Tokyo)"

removedInput schema / required

Removed value: -[
-  "timezone",
-  "formatStr"
-]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "time": {
+      "description": "フォーマット済みの現在時刻",
+      "type": "string"
+    },
+    "timezone": {
+      "description": "使用したタイムゾーン",
+      "type": "string"
+    }
+  },
+  "required": [
+    "time",
+    "timezone"
+  ],
+  "type": "object"
+}

First observedFeb 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds valuable behavioral details beyond annotations, such as date-fns format support, example format strings, and the specific instruction to use 'HH' for 24-hour notation.

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 concise—two sentences that are front-loaded with the core purpose, followed by relevant format guidance. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For this simple tool, the description covers the essential usage aspects: timezone, format string, examples, and the 24-hour notation caveat. The presence of an output schema and thorough parameter descriptions means no additional return-value documentation is needed.

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 schema descriptions already cover both parameters fully (100% coverage), but the description enriches understanding by providing concrete format examples and clarifying 24-hour notation behavior, which goes beyond the schema's basic definitions.

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 tool retrieves the current time for a specified timezone using the verb '取得' (get) with a specific resource. It distinguishes itself from sibling tools about city lists and real estate prices, and includes concrete format examples.

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?

The description provides clear context on when to use the tool (get current time in a timezone) and explains the format string syntax with examples. It does not explicitly mention alternatives or exclusions, but siblings are unrelated, so no additional differentiation is needed.

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

All 不動産情報サービス MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get-time retrieves current time, reinfolib-city-list gets city codes, and reinfolib-real-estate-price gets price data. No overlap in functionality.

Naming Consistency2/5

Naming is inconsistent: 'get-time' uses a kebab-case verb-noun pattern, while 'reinfolib-city-list' and 'reinfolib-real-estate-price' use snake_case with a 'reinfolib-' prefix and different term order. No uniform convention.

Tool Count2/5

Only 3 tools, which is too few for a real estate information service. The inclusion of 'get-time' seems unrelated and suggests the server may have a mixed or ambiguous scope.

Completeness2/5

Missing essential tools like prefecture list, station list, property details, or search by multiple criteria. The set covers only city lookup and price, leaving significant gaps for real estate information retrieval.

Resources

Need Help?