Liki — Professional AI Astrologer (moved)

This connector has been deprecated

instead by hk.liki/liki

time_now

Read-onlyIdempotent

按 IANA 时区返回服务端当前标准时间（无 DST）；空值、无效或未知 timezone 直接报错。所有「现在/今天/当前年份」运算以本返回值为唯一时间基准。用户出生时间不走本工具：民用/农历/时辰/日界模糊时先用 subject_candidates；地点或时区未知先用 city_info；黄历择日用 huangli_days。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timezone": "<timezone>"
    },
    "name": "time_now"
  }
}

Input Schema

Name	Required	Description	Default
`timezone`	Yes	IANA timezone, e.g. Asia/Shanghai. Required.

Output Schema

Name	Required	Description	Default
`local_standard_time`	Yes	当前时区标准时间（无 DST），RFC3339。

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint), and the description adds real behavior beyond them: no DST is applied, and empty/invalid/unknown timezone fails fast rather than returning a default. It does not describe the error shape or confirm whether resolution happens server-side versus validated per IANA database, leaving a small gap for a time-base tool other tools depend on.

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?

Four compact clauses, each doing distinct work: core behavior plus DST caveat, error semantics, canonical-usage rule, and negative routing. Front-loaded with the primary capability and contains no restatement of the tool name or filler.

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?

An output schema exists, so return-value documentation is unnecessary, and the description instead covers what the schema cannot: DST behavior, error conditions, and the fact that this value is the reference time for other computations. For a single-parameter tool this is fully sufficient to call correctly.

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?

Schema coverage is 100% and already documents the single required IANA timezone parameter, so the baseline is 3. The description still adds value by defining the failure semantics for empty, invalid, and unknown timezone values, which the schema does not specify.

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?

States a specific verb and resource ('按 IANA 时区返回服务端当前标准时间') and immediately qualifies the semantics with '(无 DST)'. An agent can distinguish this from every sibling listed (city_info, huangli_days, subject_candidates) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the canonical use case ('所有「现在/今天/当前年份」运算以本返回值为唯一时间基准') and enumerates when NOT to use it, routing birth-time cases to subject_candidates, unknown location/timezone to city_info, and almanac selection to huangli_days. When/when-not/alternatives are all present.

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

All Liki — Professional AI Astrologer (moved) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?