Star Ninja reports sky darkness, cloud cover and moonless hours for a night-sky spot you name.
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or misselection between tools. Its purpose, while somewhat vague, is distinct by default.
The single tool name 'inspect_observing_spot' follows a clear verb_noun snake_case pattern. There are no other names to conflict with, so consistency is trivially perfect.
A single tool feels thin for a server named Star Ninja, implying a broader astronomy or observation domain. While a focused server could justify one tool, this count is borderline inadequate.
The surface covers only inspecting an observing spot and selecting a returned night, with no tools for creating, listing, updating, or managing spots, nights, or other astronomy data. Significant gaps will likely cause agent failures for typical stargazing workflows.
Inspect your spot from your start and optionally select a returned night.
| Name | Required | Description | Default |
|---|---|---|---|
| nightDate | No | ||
| spotLatitude | Yes | ||
| spotLongitude | Yes | ||
| startLatitude | Yes | ||
| startLongitude | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so the safety profile is covered, but the description adds almost no behavioral context: it does not say what is returned, whether "inspect" computes visibility/conditions, or how selecting a night behaves. The only extra signal is that a night selection is optional.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single short, front-loaded sentence with no filler, which is structurally good. The problem is under-specification rather than verbosity, so it is concise but not informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 5 parameters, 0% schema coverage, no output schema, and no annotations beyond readOnlyHint, the description carries the full explanatory burden and does not meet it. An agent cannot tell what the tool returns or how the coordinates are used.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across 5 parameters, four of them required coordinates. The description only loosely maps "from your start" to the startLatitude/startLongitude pair and "night" to nightDate; it never explains the distinction between start and spot coordinates or the required date format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Inspect your spot from your start" largely restates the tool name (inspect_observing_spot) without saying what the inspection produces or what an "observing spot" means. The added clause about selecting a returned night hints at a two-step flow but does not clarify the resource or result.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this tool, when not to, or what alternatives exist (there are no siblings, so no routing is needed). The "optionally select a returned night" phrasing implies a follow-up step but never states the condition for using it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
inspect_observing_spotLive stargazing forecasts: per-night sky scores, dark-sky sites, aurora & light pollution anywhere.
Observational astronomy in one place
Offline observational astronomy: positions, rise/set, moon phases, eclipses, and seasons.
Astronomy: sun, moon, planet, eclipse, twilight and star position calculations.
Add one secure layer between your agents and this server.
