Skip to main content
Glama

AutoTasker Hub — China Social Data API

lunar_calendar

Solar-lunar conversion with Ganzhi, zodiac, festivals. Local compute. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
dateNotoday

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two genuinely useful traits: computation is local, and the call costs $0.01 USDC. It does not address payment mechanics (wallet, auth, whether the charge occurs on failure), out-of-range or malformed date behavior, or what the caller receives back. Those omissions matter for a paid, unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core function, with zero filler sentences. However, the telegraphic fragment style ('Ganzhi, zodiac, festivals. Local compute. $0.01 USDC.') trades clarity for brevity, and terms like 'Ganzhi' are presented without context a typical agent can act on.

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

Completeness2/5

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

For a one-input, paid, unannotated tool with no output schema, the description should at minimum pin down input format, conversion direction, and return shape. It delivers only a feature list and pricing, so an agent could easily call it with a badly formatted date or misinterpret the result.

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?

The schema documents a single optional 'date' parameter with a 'today' default but carries 0% description coverage, so the description needed to compensate. It says nothing about the parameter at all: no accepted format (ISO vs. lunar string), no difference in meaning between supplying a solar versus a lunar date, and no note that omission yields today. That leaves the only input underspecified.

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?

The description names a specific resource and operation set: solar-lunar conversion plus Ganzhi, zodiac and festival data. That is far more informative than the bare tool name. It stops short of a 5 because it never states conversion direction (solar to lunar, lunar to solar, or bidirectional), which is the single most important disambiguation for this function.

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?

There is no statement of when to invoke this tool versus anything else, no prerequisites, and no indication of which calendar direction or range of dates is supported. The reader is left to infer usage entirely from the feature list.

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.