Skip to main content
Glama

Get Chinese Astrology

Annual flying stars

get_flying_stars
Read-onlyIdempotent

Returns the annual Flying Stars chart for a year: the star in each of the nine palaces, the centre star and the moment Li Chun begins the year. The grid has south at the top.

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

Input Schema

NameRequiredDescriptionDefault
yearYesYear from 1900 to 2099.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false, openWorld false), so the bar is lower; the description nonetheless adds a genuinely non-obvious output convention — 'the grid has south at the top' — that an agent could otherwise misread. It also names the Li Chun year boundary, which clarifies how the chart is anchored. It stops short of describing error behavior for out-of-range years, but the schema handles that.

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?

Two sentences, zero filler. The core purpose comes first, the returned contents second, and the orientation caveat last where it is most needed. No sentence could be removed without losing information.

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 rich annotations, full schema coverage, and an output schema that carries the return shape, the description only needs to supply orientation and domain framing — which it does. The only minor gap is the absence of any note about invalid or out-of-range year handling or how the chart relates to sibling astrological tools, though the schema range constraint largely covers the former.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'year' parameter is already documented with a 1900–2099 range, establishing a baseline of 3. The description adds meaning beyond that by tying the year to the moment Li Chun begins, signalling that this is a solar-term-defined year rather than a calendar year — a distinction an agent would not obtain from the schema alone.

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?

A specific verb ('Returns') plus a precisely bounded resource ('the annual Flying Stars chart for a year'), followed by an enumeration of the chart's contents: the star in each of the nine palaces, the centre star, and the Li Chun boundary moment. Nothing in the sibling set (bazi, kua, zi wei, zodiac year) overlaps with this resource, so an agent can select it without opening the schema.

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?

The scope word 'annual' and the required year argument make the intended use case evident, but there is no explicit statement of when to prefer this over related tools (e.g., a natal or month-level chart) and no exclusions or prerequisites. Usage must be inferred rather than read.

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.