Vigi-Sky

Vigi-Sky service status and counts

status

Read-onlyIdempotent

Return the health of the Vigi-Sky API, the size of the Hatch archive and the number of public observations. Use it before quoting live counts or when another tool returned an error; for identity and method use doctrine. Live, cached 30 seconds to 2 minutes.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`citations`	Yes
`provenance`	Yes
`mcp_version`	No
`availability`	No
`public_consented_dossiers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedOutput schema / description

Added value: +"Returns availability, mcp_version, public_consented_dossiers, counts, citations, provenance."

Changed1 schema field changedAug 18, 2026
- addedOutput schema / required
```
Added value: +[
+  "citations",
+  "provenance"
+]
```
First observedAug 17, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description's genuinely additive detail is the caching window ('cached 30 seconds to 2 minutes'), which tells the agent figures may be stale — useful, but no mention of which values live vs. cached, rate limits, or error behavior.

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?

Two sentences, front-loaded with what is returned, then when to use it. No filler, and the caching note is appended compactly rather than as a separate paragraph.

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?

A zero-argument status tool with an output schema, so return-shape explanation is unnecessary, and the freshness caveat plus error-recovery guidance covers what an agent needs. Nothing required for correct invocation is missing.

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 takes no parameters, so the baseline is 4; there is nothing for the description to disambiguate. The enumeration of what comes back is helpful orientation even though the output schema already defines it.

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?

States a specific verb ('Return') and enumerates the exact resources returned: API health, Hatch archive size, public observation count. It is clearly distinct from most siblings, though it never distinguishes itself from hatch_stats, which likely overlaps on archive figures.

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 two concrete triggering conditions ('before quoting live counts' and 'when another tool returned an error') and routes a different need (identity and method) to the named sibling doctrine. An agent knows both when to call this and where to go instead.

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?