Skip to main content
Glama

Jiaheniao Tibetan Calendar

get_day_mechanism

Read-onlyIdempotent

查询实际公历日期是否为藏历重日第二次、此前跳过哪些日号;缺日不是该公历日不存在。仅2026、2027。

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": {
      "date": "<date>"
    },
    "name": "get_day_mechanism"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes严格有效的公历YYYY-MM-DD;仅已核2026、2027年。

Output Schema

NameRequiredDescriptionDefault
dataYes
errorYes
statusYes
source_urlYes
attributionYes
data_versionYes
source_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by scoping support to 2026/2027 and by warning that a missing day in the Tibetan calendar does not mean the Gregorian date is invalid — a semantic caveat an agent would otherwise misread. It does not say what happens when a caller passes an out-of-range year.

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?

It is short, but it is a single dense semicolon-chained clause in domain jargon, and the hard scope limit (2026, 2027) is buried at the very end rather than front-loaded. The caveat sentence earns its place; the dual-query phrasing does not read cleanly.

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

Completeness3/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 structure need not be explained. However, for a niche domain tool the description leaves the out-of-range behavior undefined and does not clarify how the 'second duplicate day' and 'skipped day numbers' results relate, which is the one thing an agent cannot infer from the schema.

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% and the single parameter already documents the strict YYYY-MM-DD format and the 2026–2027 verification scope. The description only repeats the year restriction, adding no new syntax or format meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete query object — whether a given Gregorian date is the second occurrence of a Tibetan calendar duplicate day, plus which day numbers were skipped — but it bundles two distinct outputs into one verb ('查询…是否为…;此前跳过哪些日号'), leaving the primary result ambiguous. Nothing in the text distinguishes it from the sibling convert_gregorian_to_tibetan.

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

Usage Guidelines2/5

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

The only usage constraint given is the year scope ('仅2026、2027'), which is a validity boundary rather than when-to-use guidance. There is no statement about when an agent should pick this over convert_gregorian_to_tibetan or get_year_festivals, and no exclusion criteria beyond the years.

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