Skip to main content
Glama
Sign In

Qimena Qi Men Dun Jia & BaZi

by io.github.David-rider
OverviewDiscussionsAdmin

Solar terms of a year

solar_terms
Read-onlyIdempotent

The 24 solar terms (节气) of a calendar year, 1900-2100, with UTC and Beijing-time instants from the same table the charts use (within about a minute of the Hong Kong Observatory).

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": {
      "year": "<year>"
    },
    "name": "solar_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description only needs to add context. It does that usefully by disclosing the data source, dual time zones (UTC and Beijing), and an accuracy bound relative to the Hong Kong Observatory.

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?

A single front-loaded sentence with the resource and range stated first, followed by the time-zone and accuracy qualifiers. No wasted text.

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?

With no output schema, the description usefully signals what is returned (instants in UTC and Beijing time) and the year bounds. It could say more about the shape of the returned list, but is adequate for a one-parameter lookup.

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 is fully documented, so the schema carries the semantics. The description restates the 1900-2100 range already enforced by the schema's min/max, adding no new syntax or format detail.

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

Purpose4/5

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

States the specific resource (the 24 solar terms) and scope (a calendar year, 1900-2100), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from the sibling tools, but the resource is distinctive enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is only implied: needing solar-term dates/times for a given year. There is no statement of when to use this over bazi_pillars, best_times, or qimen_chart, nor any prerequisites or exclusions.

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

All Qimena Qi Men Dun Jia & BaZi toolsInspect
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