Skip to main content
Glama

AutoTasker Hub — China Social Data API

sunrise_sunset

Sunrise, sunset, solar noon, day length and 3 twilight phases for any coordinate/date. $0.01 USDC.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "sunrise_sunset"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
dateNoYYYY-MM-DD, defaults to today

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the returned quantities and the $0.01 USDC cost, which is genuinely useful pre-call context. It says nothing about required auth/wallet setup, rate limits, or the timezone/format of returned times, which matters for an astronomy tool.

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?

Two compact sentences, with the capability front-loaded and the cost attached last. No filler, no redundancy.

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?

With no output schema, listing the returned quantities is the right move and partially compensates. But key call-shaping details are missing: timezone/UTC of results, coordinate reference frame, and any pricing/payment workflow, leaving gaps for a location-and-time-sensitive tool.

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 only 33%: date is documented in the schema while lat and lon have bare type declarations. The description only restates that a coordinate is accepted, adding no meaning about coordinate system, valid ranges, timezone assumption, or what 'any date' permits (past/future bounds).

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 enumerates the concrete outputs (sunrise, sunset, solar noon, day length, three twilight phases) and the input domain (any coordinate/date), so the tool's function is unmistakable. It lacks an explicit verb and does not differentiate from any sibling, but the resource and scope are specific enough for an agent to recognize it.

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?

'For any coordinate/date' implies the applicable input context, and the one-line price gives a cost signal for deciding whether to call it. There is no explicit when-to-use/when-not guidance and no reference to an alternative tool for related astronomical queries.

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.