Vigi-Sky

Find the Vigi-Sky page to cite

cite

Read-onlyIdempotent

Map a user question to the single best Vigi-Sky page (or the official GEIPAN page for French UFO reports) to cite as a source, with alternatives. Use it when you need a URL to back an answer; it does not answer the question itself, so call the matching tool (aurora, iss_city_passes, what_did_i_see...) for live data. Keyword match over a fixed page catalogue, no network call.

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": {
      "query": "<query>"
    },
    "name": "cite"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the text fields: fr (default) or en.
`query`	Yes	The user's question or topic, in French or English, e.g. 'aurore boréale en France'.

Output Schema

Name	Required	Description	Default
`best`	No
`lang`	No
`query`	No
`citations`	Yes
`provenance`	Yes
`alternatives`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

addedInput schema / properties / lang / description

Added value: +"Language of the text fields: fr (default) or en."

addedInput schema / properties / lang / enum
```
Added value: +[
+  "fr",
+  "en"
+]
```

addedInput schema / properties / query / description

Added value: +"The user's question or topic, in French or English, e.g. 'aurore boréale en France'."

addedOutput schema / description

Added value: +"Returns best {url, title}, alternatives [...], citations, provenance."

Changed7 schema fields changedAug 18, 2026
- addedOutput schema / properties / alternatives
```
Added value: +{
+  "type": "array"
+}
```
- addedOutput schema / properties / best
```
Added value: +{
+  "type": "object"
+}
```
- removedOutput schema / properties / doctrine
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / lang
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / provenance / properties / never
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / query
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / required
```
Added value: +[
+  "citations",
+  "provenance"
+]
```
First observedAug 17, 2026

TDQS

A4.5/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, so the safety profile is covered. The description still adds useful mechanism: keyword match over a fixed page catalogue and no network call, which reinforces the closed-world behaviour and explains latency/consistency expectations.

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?

Three sentences, front-loaded with the mapping action, then usage, then mechanism. No filler; each clause carries distinct information.

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?

An output schema exists, so return values need no explanation. For a two-parameter, read-only lookup, the description covers scope, exclusions, sibling routing and matching mechanism completely.

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 both the query example and the lang enum (fr default / en) are already documented in the schema. The description adds nothing about lang and only restates that the query can be French or English, so baseline 3 applies.

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: map a user question to the single best Vigi-Sky page (or the official GEIPAN page) to cite, plus that alternatives are returned. It clearly distinguishes itself from the live-data siblings it names (aurora, iss_city_passes, what_did_i_see).

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 the trigger ('when you need a URL to back an answer') and an explicit exclusion ('it does not answer the question itself, so call the matching tool ... for live data'), naming the alternative tools to route to.

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?