Vigi-Sky

Map of Vigi-Sky MCP servers

capabilities

Read-onlyIdempotent

Describe what this public server offers and what the separate local server (VigiSky Sentinel, 23 tools, runs on the user's PC) adds: photo and video analysis, night watch, star-field solving. Use it when a task needs local files or a camera, which this server cannot access; for sky questions this server answers directly, call the matching tool (what_did_i_see, iss_city_passes, aurora...). Static description, no network call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capabilities"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`citations`	Yes
`provenance`	Yes
`this_server`	No
`local_server`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedOutput schema / description

Added value: +"Returns this_server {n_tools, tools}, local_server {workflows, install}."

Changed5 schema fields changedAug 18, 2026
- removedOutput schema / properties / doctrine
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / local_server
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / provenance / properties / never
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / this_server
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / required
```
Added value: +[
+  "citations",
+  "provenance"
+]
```
First observedAug 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld=false. The description adds useful context beyond that: it is a static description with no network call, and it clarifies that this server cannot access local files or a camera. That helps prevent incorrect invocation, though it does not add much more behavioral depth.

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 front-loaded with purpose, followed by routing guidance and a key behavioral note. It is efficient overall, though the second sentence is long and packs several clauses; it still earns its place by clarifying server boundaries.

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 static, zero-parameter capabilities tool with an output schema, the description is complete: it explains what the tool describes, when to use it, when not to use it, and that no network call occurs. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing parameter-level to document. The schema is empty and fully covered; the baseline for a no-parameter tool is 4, and no additional parameter semantics are needed or missing.

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?

States a specific verb and resource: it describes what the public server offers and what the separate local VigiSky Sentinel server adds (photo/video analysis, night watch, star-field solving). It also explicitly distinguishes itself from sibling tools by directing sky questions to what_did_i_see, iss_city_passes, aurora, etc.

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?

Gives explicit when-to-use guidance ('when a task needs local files or a camera') and explicit when-not guidance ('for sky questions this server answers directly, call the matching tool'), naming alternatives. The boundary between this server and the local server is unambiguous.

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

All Vigi-Sky tools Inspect

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

Need Help?