Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

时间戳时区换算

time-tool

时间戳时区换算:Unix 秒 / 毫秒时间戳与日期互转,输出 UTC ISO、北京时间、星期、年内第几天、是否闰年、当月天数,支持 addDays 天数加减。处理日志、订单时间、账期时免踩时区坑。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "input": "<input>"
    },
    "name": "time-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesUnix 秒/毫秒时间戳或日期
addDaysNo可选:天数加减

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose that the operation is a deterministic pure calculation returning results '与依据', which reassures the agent there are no side effects. However, it never states how a bare number is disambiguated between seconds and milliseconds, what happens on invalid input, or whether errors are raised or returned — real gaps for a tool whose whole job is parsing ambiguous input.

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 core capability and output list are front-loaded in the first clause, and the effort is well spent. The closing sentences lean slightly promotional ('免踩时区坑', '模型算数不稳') but still serve a routing purpose, so there is little dead weight.

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?

There is no output schema, so the description correctly takes on the job of enumerating return fields, and it does so thoroughly. For a two-parameter calculator it is nearly complete; the missing piece is any statement about output container/format or behavior on unparseable input.

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 coverage is 100%, so the schema already defines both fields. The description reiterates the accepted input forms and that addDays is a day-level offset, but adds no detail on negative values, unit of addDays, or the seconds-vs-milliseconds heuristic, so it does not meaningfully exceed the schema.

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 names a specific verb and resource ('Unix 秒/毫秒时间戳与日期互转') and then enumerates exactly what is produced: UTC ISO, Beijing time, weekday, day-of-year, leap-year flag, days in month. This is far more specific than the title alone, and the sibling list contains no other time/date utility it could be confused with.

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 gives concrete when-to-use triggers ('处理日志、订单时间、账期', '模型算数不稳、法规口径易错时'), which tells the agent to prefer it over doing arithmetic in-head. It stops short of stating when not to use it or any exclusions, so it falls just below the explicit-alternatives bar.

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.