Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-zodiac-sign

Zodiac Sign: Maps the UTC month and day of a date to a Western zodiac sign name and returns it with the ISO date 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-zodiac-sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / date / description
      Removed value: -"Date to process"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the UTC-based mapping rule, the return content (zodiac sign plus ISO date), and a free trial limit tied to a signed wallet. However, it omits date format expectations, invalid-input behavior, and full payment/auth mechanics, leaving meaningful gaps for a paid x402 tool.

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?

The description is a single, front-loaded sentence that gets straight to the purpose. The free-trial note is useful context for an x402 paid tool, but the leading 'Zodiac Sign:' label slightly duplicates the tool name. Overall it is appropriately sized and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter computation tool with no output schema and no annotations, the description should explain both input expectations and return behavior. It states the return includes a zodiac sign name and ISO date, which is helpful, but it leaves the input date format unspecified and does not describe error handling or output structure in enough detail. It is minimally adequate but has clear gaps.

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 description coverage is 0% for the single 'date' string parameter. The description adds that the parameter is a date whose UTC month and day are used, which gives semantic context beyond the bare schema. It does not specify expected input format or edge cases, so it only partially compensates for the coverage gap.

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 uses a specific verb+resource pattern: it maps a date's UTC month and day to a Western zodiac sign name. It also explicitly differentiates itself from the sibling x402-chinese-zodiac by specifying 'Western' and states the return shape. An agent can identify its function 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 Guidelines2/5

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

The description gives no explicit guidance about when to use this tool versus alternatives such as x402-chinese-zodiac or x402-date. It only describes the computation and mentions a free trial limit. No conditions, exclusions, or sibling recommendations are provided.

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.