Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-chinese-new-year

Chinese New Year: Returns the Chinese New Year date for years 2023-2030 from a fixed table, with a note otherwise 🆓 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-chinese-new-year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
inputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / year / description
      Removed value: -"Year to process"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two genuinely useful traits: the result comes from a fixed table (no live computation or network dependency) and out-of-range years return a note rather than an error, plus the pricing model (5 free trial calls per signed wallet). It does not describe the response shape, error conditions, or which parameter is actually consumed.

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?

A single front-loaded sentence that leads with the resource and immediately gives the range constraint. The trailing pricing/trial badge is mildly promotional noise but costs only a few words and is arguably useful cost context.

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 lookup tool with no output schema, the description covers the data source, the supported range, the out-of-range fallback, and the pricing model. The gap is input documentation: two parameters at 0% schema coverage with one ("input") entirely undefined is not enough for an agent to invoke confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and there are two parameters, so the description must compensate. It implies the meaning of "year" by bounding the valid range to 2023-2030, but the "input" parameter is never mentioned or explained anywhere, leaving half the input surface completely opaque.

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 and resource ("Returns the Chinese New Year date") and adds the crucial scope constraint (years 2023-2030 from a fixed table), which tells the agent exactly what data is available. It doesn't explicitly differentiate itself from the adjacent x402-chinese-zodiac or other date tools, but the range constraint makes the boundary clear enough in practice.

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?

"with a note otherwise" implies the behavior for out-of-range years, which is useful usage context, and the 2023-2030 range implicitly scopes valid inputs. However, there is no explicit when-to-use guidance, no naming of alternatives (e.g., x402-chinese-zodiac for zodiac animals), and no statement of what the caller must supply.

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.