Skip to main content
Glama
Sign In

Vigi-Sky

by fr.vigi-sky
OverviewDiscussionsAdmin

Name a star or planet

which_star
Read-onlyIdempotent

Name the bright star, planet or Moon closest to a direction (azimuth, elevation) at a place and time, within 15 degrees. Use it for a steady point of light; for something that moved use what_did_i_see, for a precise satellite match use identify. Bright objects only (about magnitude 1.5 or brighter); refraction near the horizon is not modelled.

Input Schema

NameRequiredDescriptionDefault
azYesDirection in degrees from true north, clockwise: 0 = north, 90 = east, 180 = south, 270 = west.
elYesHeight above the horizon in degrees: 0 = horizon, 90 = straight overhead.
latYesObserver latitude in decimal degrees, WGS84 (north positive).
lngNoObserver longitude in decimal degrees, WGS84 (east positive). lon and lng are aliases: give one.
lonNoObserver longitude in decimal degrees, WGS84 (east positive). lon and lng are aliases: give one.
langNoLanguage of the text fields: fr (default) or en.
timeNoMoment of the observation, ISO-8601 (default now).

Output Schema

NameRequiredDescriptionDefault
bestNo
othersNo
citationsYes
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / az / description
      Added value: +"Direction in degrees from true north, clockwise: 0 = north, 90 = east, 180 = south, 270 = west."
    • addedInput schema / properties / el / description
      Added value: +"Height above the horizon in degrees: 0 = horizon, 90 = straight overhead."
    • addedInput schema / properties / lang / description
      Added value: +"Language of the text fields: fr (default) or en."
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude WGS84"New value: +"Observer latitude in decimal degrees, WGS84 (north positive)."
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude WGS84 (lon or lng)."New value: +"Observer longitude in decimal degrees, WGS84 (east positive). lon and lng are aliases: give one."
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude WGS84 (lon or lng)."New value: +"Observer longitude in decimal degrees, WGS84 (east positive). lon and lng are aliases: give one."
    • changedInput schema / properties / time / description
      Previous value: -"ISO-8601 with time zone, e.g. 2026-11-01T21:30:00+01:00 (default: now). Last 10 days to next 2 days."New value: +"Moment of the observation, ISO-8601 (default now)."
    • addedOutput schema / description
      Added value: +"Returns best {name, kind, az, el, separation_deg}, others [...], asked, note."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, open-world lookup. The description adds meaningful behavioral limits beyond the schema: the 15-degree match radius, the brightness threshold, and that refraction near the horizon is not modelled.

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?

The description is front-loaded with the core action and scope, then immediately gives alternatives and limitations. Every sentence carries useful selection or behavior information with no filler.

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?

With an output schema available and rich annotations, the description does not need to explain return values or safety. It covers the key operational constraints: 15-degree matching, bright-object limitation, and unmodelled horizon refraction.

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 description coverage is 100%, so azimuth, elevation, latitude, longitude aliases, language, and time are already well documented in the input schema. The description mentions direction and place/time but adds no parameter-level detail beyond the schema.

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 states a specific verb ("Name") and resource ("bright star, planet or Moon") plus scope (closest to a direction, within 15 degrees). It clearly distinguishes this tool from siblings by naming what_did_i_see for moved objects and identify for precise satellite matches.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool (steady point of light) and when to use alternatives (what_did_i_see for movement, identify for precise satellite matching). It also gives a key exclusion: bright objects only, about magnitude 1.5 or brighter.

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

All Vigi-Sky 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