Skip to main content
Glama

7timer

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Stargazing Forecast

stargazing_forecast
Read-onlyIdempotent

Astronomy observing forecast from 7Timer! ASTRO — the metrics stargazers and astrophotographers use to decide if tonight is good for observing: cloud cover, atmospheric seeing (steadiness), and sky transparency, at 3-hour resolution out to 72 hours. Each point gets a human-readable label and an observing_quality verdict, plus a best_window summary of the clearest/steadiest hours. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoHow far ahead to forecast, in hours (default 24, max 72). Returned at 3-hour steps.
latitudeYesLatitude in decimal degrees, e.g. 38.9.
longitudeYesLongitude in decimal degrees, e.g. -77.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 38.9,
+    "longitude": -77
+  },
+  {
+    "hours": 72,
+    "latitude": 51.5,
+    "longitude": -0.1
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable output context: human-readable labels, an observing_quality verdict, best_window summary, and 3-hour resolution up to 72 hours. This exceeds the minimum transparency bar and provides concrete behavioral details beyond the annotations.

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 concise and front-loaded, with the key purpose stated first, followed by metrics and output details. It uses efficient punctuation and includes only one minor extra ('Keyless') at the end. It is not overly verbose and every sentence contributes value.

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?

Despite having no output schema, the description adequately explains what the tool returns: metrics, human-readable labels, an observing_quality verdict, and a best_window summary. It also specifies time range and resolution. This is sufficient for an agent to understand the tool's full behavior and output.

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%, so all three parameters are already clearly described. The description adds no new parameter-level semantics beyond restating the 3-hour resolution and 72-hour max, which the schema already covers. The baseline of 3 applies because the schema carries the full burden.

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 identifies the tool as an astronomy observing forecast from 7Timer! ASTRO, listing specific metrics (cloud cover, seeing, transparency) and differentiating it from generic weather forecasts. The verb 'forecast' plus resource 'astronomy observing' is specific and distinguishes it from sibling tools like weather_forecast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies its intended use case: 'the metrics stargazers and astrophotographers use to decide if tonight is good for observing.' It also notes the tool is 'Keyless,' which is a practical usage detail. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

All 7timer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources