Skip to main content
Glama

Stargazing Conditions

get_stargazing_conditions
Read-onlyIdempotent

Returns tonight's stargazing forecast for Sedona, AZ — astronomical darkness window, moon interference, Milky Way galactic core visibility, and best times to shoot the night sky. Sedona sits near the Verde Valley Dark Sky corridor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD (default tonight)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
moonYes
sourceYes
darknessYes
locationYes
milky_wayYes
top_sitesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "darkness": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "astronomical_twilight_begin": {
      +          "type": "string"
      +        },
      +        "astronomical_twilight_end": {
      +          "type": "string"
      +        },
      +        "note": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "astronomical_twilight_end",
      +        "astronomical_twilight_begin",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "date": {
      +      "type": "string"
      +    },
      +    "location": {
      +      "type": "string"
      +    },
      +    "milky_way": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "note": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "status",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "moon": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "emoji": {
      +          "type": "string"
      +        },
      +        "illumination_pct": {
      +          "type": "number"
      +        },
      +        "interference_rating": {
      +          "type": "string"
      +        },
      +        "moon_age_days": {
      +          "type": "number"
      +        },
      +        "note": {
      +          "type": "string"
      +        },
      +        "phase": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "phase",
      +        "emoji",
      +        "illumination_pct",
      +        "moon_age_days",
      +        "interference_rating",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "top_sites": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "why": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "why"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "location",
      +    "darkness",
      +    "moon",
      +    "milky_way",
      +    "top_sites",
      +    "source"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering safety. The description adds value by specifying the return content (astronomical details) and location context, but does not disclose extra traits like rate limits or data sources.

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 sentences, both essential and front-loaded. No redundancy or fluff.

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

Completeness5/5

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

For a tool with one optional parameter, strong annotations, and an output schema (assumed present), the description provides sufficient context: location, return components, and default behavior.

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 coverage is 100% with the 'date' parameter described ('Date YYYY-MM-DD default tonight'). The description reinforces 'tonight' but adds no new meaning beyond the schema. Hence baseline 3.

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 clearly states it returns a stargazing forecast for Sedona, AZ, listing specific components (darkness window, moon interference, Milky Way visibility, best times). This distinctively separates it from siblings like get_moon_phase or get_sun_times.

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?

The description implies use for stargazing planning in Sedona but does not explicitly state when to use versus alternatives (e.g., other location tools, or when not to use). No mention of exclusions or paired tools.

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.

Resources