Skip to main content
Glama
Sign In
TimezoneToolkit MCP Server

TimezoneToolkit MCP Server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_moon_phase

Calculate the moon phase for a specific date, optionally in a given timezone, to obtain lunar phase details for astronomy or planning.

Instructions

Calculate moon phase for a specific date

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate for calculation (ISO string or natural language). Defaults to current date.
timezoneNoIANA timezone name (e.g., 'Europe/Paris'). Defaults to UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior1/5

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

No annotations are provided, and the description gives no behavioral details such as calculation method, handling of timezone, what output to expect, or any edge conditions. This leaves the agent fully in the dark about the tool's behavior.

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 sentence with no redundancy or wasted words, making it very concise. However, it lacks any structural elements (e.g., separate sections) but that is acceptable for a tool of this simplicity.

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?

There is no output schema, so the description would need to explain what the tool returns, but it does not. While the tool is simple with only two parameters, the missing return-value information and lack of any usage context make it incomplete.

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?

The input schema fully documents both parameters (date and timezone) with helpful descriptions and defaults, so the baseline score of 3 applies. The description adds no additional parameter meaning beyond the general notion of a date.

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 the specific verb 'calculate' with resource 'moon phase' and scope 'specific date', clearly stating the tool's purpose and distinguishing it from sibling time/date tools.

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?

No explicit guidance on when to use this tool versus alternatives. The description merely states what it does; it does not mention exclusions or present alternative tools for comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools