Skip to main content
Glama

Jiaheniao Tibetan Calendar

convert_gregorian_to_tibetan

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": "convert_gregorian_to_tibetan"
  }
}

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

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context beyond the annotations by emphasizing that only reviewed calendar data is used and that results include month-name basis and source links.

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 compact and front-loaded: conversion purpose, supported years, no extrapolation, and return content are all stated without redundant wording.

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?

Given the single required parameter, the existing output schema, and the read-only annotations, the description supplies the key operational constraints an agent needs: verified-only data, no extrapolation, and supported years. Nothing essential for correct invocation is missing.

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 description coverage is 100%, and the schema already specifies a strict YYYY-MM-DD Gregorian date limited to verified 2026 and 2027. The description reinforces the same year restriction but does not add syntax or format details beyond what the schema provides, so the high-coverage baseline applies.

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 states a specific verb and resource: converting a Gregorian date to a verified Tibetan calendar date. It also clearly scopes the operation to 2026 and 2027 and says no extrapolation is performed, which distinguishes it from the sibling tools get_day_mechanism and get_year_festivals.

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 gives an explicit usage boundary: only verified 2026 and 2027 dates are supported, and no extrapolation is done. It does not name an alternative tool for other years, but the year restriction and no-extrapolation rule make the intended use clear.

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