Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Zodiac sign from a birth date: western and Chinese

date_zodiac
Read-only

Western (tropical) zodiac sign with its element, and the Chinese zodiac animal and element of a birth date. The Chinese year is counted from the Gregorian year, so dates in January and early February before Chinese New Year are flagged as possibly the previous animal. Use for profile enrichment, greeting cards, games or horoscope-style content. Example: date=1990-08-15. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the basic safety profile is known. The description adds material context beyond that: per-call pricing with a free tier, the fact that repeated calls are charged, failed calls being free, and the important caveat that January/early-February dates may map to the previous Chinese animal. It restates the 'changes nothing' claim already covered by annotations, which keeps it from a 5.

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?

Purpose is front-loaded in the first sentence, followed by the caveat, uses, example, and billing. The pricing/card-key sentence is somewhat boilerplate-heavy, but every clause carries actionable information and there is no filler.

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 one-parameter, no-output-schema computation tool, the definition covers inputs, expected outputs (sign, element, animal), a known ambiguity, and cost. Only the exact shape of the returned fields is unspecified, which is a minor gap given the absence of an output schema.

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?

With a single parameter at 100% schema coverage, the schema already documents the YYYY-MM-DD format, so the baseline is 3. The description contributes an example value and explains an edge case in how the date is interpreted (pre-Chinese New Year dates), which adds some meaning but is mostly about output interpretation rather than the parameter itself.

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?

States a specific verb ('computes'/returns) and specific resources: the western tropical sign with its element, plus the Chinese zodiac animal and element, for a given birth date. This is clearly distinguishable from neighboring date tools like date_info or calc_age, since the outputs and domain are named explicitly.

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?

Gives concrete use contexts ('profile enrichment, greeting cards, games or horoscope-style content') and a worked example (date=1990-08-15), which tells an agent when this tool fits. It offers no explicit exclusions or named alternatives, so it stops short of full when-to-use/when-not 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.