Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Chinese solar terms

solar_terms
Read-onlyIdempotent

The 24 Chinese solar terms (jieqi) of a year 1900-2100, with dates in China, moments in UTC and the Chinese lunar date. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
yearNoGregorian year 1900-2100 (default this year).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/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 value beyond that by disclosing what each result contains — dates localized to China, moments in UTC, and the Chinese lunar date — which matters since there is no output schema. It does not say what happens for out-of-range years (error vs. empty), a minor remaining gap.

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?

The first sentence is dense, front-loaded, and fully earns its place. The second sentence is a promotional link with UTM tracking that adds no tool-selection value and dilutes the definition.

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 single-optional-parameter lookup with no output schema, the description adequately covers scope and return contents so an agent can call it correctly. Only edge-case behavior (invalid year handling) and the result's shape (array of 24 entries?) are left implicit.

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%: the single 'year' parameter already documents the 1900-2100 range and the current-year default. The description only echoes that range and adds no new semantics, so the baseline 3 for schema-covered parameters applies.

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?

The description names a specific resource (the 24 Chinese solar terms / jieqi) and its scope (a year, 1900-2100), which clearly separates it from siblings like holidays or calendar_months. It omits an explicit verb ('returns'/'lists'), but the noun phrase is specific enough that an agent knows what it gets.

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?

There is no guidance on when to call this instead of siblings such as holidays or convert_date, and no stated prerequisites or exclusions. The only constraint given (year range) is a parameter constraint, not usage guidance.

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