Skip to main content
Glama

Get Chinese Astrology

Five elements count

count_five_elements
Read-onlyIdempotent

Counts Wood, Fire, Earth, Metal and Water across the visible characters of the Four Pillars chart for a birth date, with an optional birth time and UTC offset. Returns each count with its relation to the Day Master, the leading element, the elements missing from view and the Day Master.

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

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date as YYYY-MM-DD, from 1901-02-19 to 2100-02-08.
timeNoLocal birth time as HH:MM on a 24-hour clock. Without it the count covers six characters instead of eight.
utcOffsetNoFixed UTC offset of the birthplace as +HH:MM or -HH:MM, used for solar-term boundaries. +08:00 when absent.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 that counting is limited to 'visible characters' and enumerates the derived outputs (relation to Day Master, leading element, missing elements), which is useful behavioral context, but it never warns about edge cases such as timezone-free calculations or the 1901-2100 date bounds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and the counted elements, with the optional inputs introduced immediately after. The second sentence is a dense comma-list of return fields that is slightly harder to scan, but no sentence is wasted.

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?

The tool is a single-purpose read with three fully documented parameters and an output schema, so the description does not need to explain return values — yet it still summarizes them, which is helpful. Nothing critical is missing for an agent to call it correctly, aside from sibling routing guidance.

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%, so format, patterns and length constraints for date, time and utcOffset are already fully documented in the schema. The description only restates that time and UTC offset are optional, adding no new semantic detail such as how the offset affects solar-term boundaries beyond what the schema says.

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 a specific verb (counts) and specific resources (Wood, Fire, Earth, Metal, Water across the visible characters of the Four Pillars chart) for a birth date. An agent can tell this is an elemental-tally tool rather than a full chart renderer like get_bazi_chart, though the description never names that sibling to make the contrast explicit.

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 implied by the stated inputs (a birth date, optional time and UTC offset), so an agent can infer it needs a birth date. There is no explicit when-to-use versus a full chart tool, and no statement of prerequisites or when the optional time/offset should be supplied beyond the schema's own explanation.

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.