Destiny Weight reading from birth date — Yuan Tiangang method.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is singular and unambiguous.
The single tool name follows a clear verb_noun pattern (calculate_destiny_weight) and accurately describes its function. There are no other tools to create inconsistencies.
One tool is on the thin side for a typical MCP server, but it is appropriately scoped for the server's narrow purpose of destiny weight calculation. The count feels minimal yet functional.
The domain is entirely covered by this single tool; it performs the full lifecycle of accepting birth date/time and returning a reading. No additional operations are needed for the stated purpose.
calculate_destiny_weightAInspectDestiny Weight: calculate your life-weight from your birth date and time, and return an English destiny reading (based on the traditional Chinese method attributed to Yuan Tiangang, adapted for Western audiences). Use when the user asks about "destiny weight", "life weight", "fate weight", or a weight-based fortune reading.
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | Birth day (1-31) | |
| hour | Yes | Birth hour (0-23) | |
| year | Yes | Birth year (Gregorian, e.g. 1990) | |
| month | Yes | Birth month (1-12) | |
| gender | Yes | Gender (affects the destiny reading) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for behavioral disclosure. It does not state whether this is a read-only calculation or if it has side effects (it likely is read-only, but the agent can't be sure). It also doesn't mention any limitations or assumptions (e.g., valid date ranges, accuracy). It adds some value by noting it's 'adapted for Western audiences' and returns an 'English' reading, but it falls short of fully disclosing behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, at about two sentences, and front-loads the core purpose. It includes the trigger phrases, which is useful for routing. It is not overly verbose, but it could be slightly more structured (e.g., separating the 'use when' clause), but overall it is efficient and free of fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description does a decent job of explaining the return value (an English destiny reading). However, it does not provide details on the format of the reading (e.g., length, structure), nor does it mention any edge cases (e.g., invalid dates). It is complete enough to allow an agent to call the tool, but not rich enough to set expectations about the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema already provides full descriptions for all 5 parameters (100% coverage), the description adds valuable context: it explains that gender affects the reading and that the method uses birth date and time. This goes beyond the schema's simple type descriptions by highlighting the significance of gender in determining the outcome. However, it doesn't add details on how each parameter influences the calculation, but that is not required given the schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool's purpose: calculating 'destiny weight' from birth data and providing an English reading. It names the specific method (Yuan Tiangang) and distinguishes it from generic fortune-telling, making it unambiguous. It also provides explicit trigger phrases, further clarifying when to use it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes specific usage triggers ('when the user asks about...'), which is strong guidance. However, it does not mention any alternative tools or when NOT to use it, but since there are no sibling tools listed, this is not a major gap. The explicit 'use when' condition is a clear guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!