Skip to main content
Glama
Sign In

asktian

by io.github.douglasgan
OverviewDiscussionsAdmin

asktian_daily_reading

Get today's personalized Chinese metaphysics (八字 bazi + 干支 daily energy) reading for a person. Returns their archetype (one of 8 trigrams 八卦), today's energy, favorable colors/direction/hours, headline advice, and any caution. Use this when the user asks how today will be for them, what colors to wear, where to face their desk, or for general daily guidance.

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": {
      "birthdate": "<birthdate>"
    },
    "name": "asktian_daily_reading"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderNoOptional. Some metaphysics traditions weigh gender; pass 'any' if unsure.
birthdateYesISO date YYYY-MM-DD (Gregorian calendar).
birth_hourNoOptional 24h time HH:MM. If unknown, omit (defaults to noon).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

No annotations provided, so description must carry behavioral info. It discloses input parameters and what is returned, but does not mention if it is read-only or any side effects. Since it's a prediction tool, the behavior is implied but not explicitly stated beyond the return content.

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?

Three sentences, front-loaded with purpose and details, no redundancy. Every sentence is informative and earns its place.

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?

Given no output schema, the description adequately lists return elements (archetype, energy, colors, direction, hours, advice, caution). All three parameters are described. However, the temporal scope ('today's') is clear from name and description, but could be explicitly reinforced.

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%, so baseline is 3. The description adds value by explaining the gender parameter ('some traditions weigh gender') and birth_hour default ('defaults to noon'), which aids correct parameter specification beyond the schema.

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?

The description clearly states it provides a personalized Chinese metaphysics reading for today, including specific elements like archetype, energy, colors, direction, hours, advice, and caution. This distinguishes it from siblings like asktian_best_time_for_action or asktian_compatibility.

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

Usage Guidelines5/5

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

Explicit instructions: 'Use this when the user asks how today will be for them, what colors to wear, where to face their desk, or for general daily guidance.' This provides clear context and implicitly tells when not to use it (e.g., for best action times or compatibility).

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

All asktian 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