Skip to main content
Glama

九玄宫奇门遁甲排盘

当前北京时间

beijing_civil_now
Read-only

返回现在的北京时间(Asia/Shanghai,固定 UTC+8,无夏令时)。 实现是 UTC 加 8 小时,不查时区数据库,也不使用调用者所在地。 用这个结果填写 cast_qimen 的 civilTime 前,先确认用户要的是“此刻”,而不是出生时间或别的时区。 这不是真太阳时。1949 年前的钟面不能用本工具回推。 Current Beijing civil time. Fixed UTC+8. Not the caller's local zone and not true solar 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": "beijing_civil_now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the implementation is a naive UTC+8 offset with no timezone-database lookup, that caller location is ignored, and that this is not true solar time. The only thing left implicit is the return value's shape (string format/precision), which matters somewhat given there is no output schema. The annotations already declare it read-only and non-idempotent, and the description is consistent with that.

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?

Front-loaded with the core answer (current Beijing time, UTC+8, no DST) before the caveats and the routing hint to cast_qimen. The trailing English sentence largely restates the Chinese body, which is mild duplication, but the total length is short and every distinct claim earns its place.

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 zero-parameter, zero-annotation-risk clock tool this covers the important ground: timezone semantics, no DST, no location dependence, not solar time, and the pre-1949 limitation. The one gap is the output format, which an agent must guess since no output schema exists.

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 there is nothing for the description to disambiguate at the argument level. Baseline for a parameterless tool applies, and nothing here misleads about inputs.

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 — returns the current Beijing civil time — and immediately pins down the exact semantics (Asia/Shanghai, fixed UTC+8, no DST). It also rules out the two most likely misinterpretations (caller's local zone, true solar time), so an agent can tell what this is and is not without inspecting anything else.

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?

Gives explicit when-to-use guidance tied to a concrete sibling: use the result to fill cast_qimen's civilTime, but only after confirming the user wants 'right now' rather than a birth time or another timezone. It also states an explicit when-not: clock faces before 1949 cannot be back-derived with this tool.

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