Skip to main content
Glama

sky_seeing

Is tonight actually usable for stargazing or astrophotography? Combines real dark hours and true moon illumination (computed from first principles) with live hourly cloud cover, weighting low cloud above high cloud. Returns a 0-100 usability score per night hour, the best consecutive usable run, and a plain verdict. lat/lon required; tz_offset and when optional.

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, -90..90.
lonYesLongitude, -180..180.
whenNoOptional ISO date/time to plan for. Default now.
tz_offsetNoHours offset from UTC for local clock labels. Default: estimated from longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that data is 'live hourly cloud cover' (implying an external/network dependency), that moon illumination is computed from first principles, that low cloud is weighted above high cloud, and what the response shape is. It does not cover failure modes, latency, or behavior at polar latitudes with no true darkness.

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?

Front-loaded with the user-facing question, then method, then return values, then parameters — a sensible information order. It is tight overall, though the 'computed from first principles' and cloud-weighting detail is method trivia that an agent calling the tool does not strictly need.

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

Completeness4/5

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

There is no output schema and no annotations, so the description must explain returns and behavior, which it does (score scale, best run, verdict, weighting). Given four simple scalar parameters, the only real omission is behavior for edge cases like polar day/night or missing cloud data.

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 the schema already documents all four parameters with ranges and defaults. The description only echoes requiredness and optionality, adding no syntax, format, or interpretation beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 opening question names the concrete decision (stargazing/astrophotography usability tonight) and the body specifies outputs: a 0-100 score per night hour, best consecutive run, and a verdict. It is a specific verb+resource, but it never distinguishes itself from nearby siblings like sky_tonight, sky_at, or moon_phase, which an agent must guess between.

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?

Usage is only implied by the framing question — an agent can infer this is for planning observing sessions. There is no explicit statement of when to prefer this over sky_tonight, sky_at, or weather, and no exclusions. The closing 'lat/lon required; tz_offset and when optional' is parameter restatement, not usage guidance.

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