Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_monitoring_snapshot

Read-onlyIdempotent

Reads the published Reliquary monitoring snapshot, preserving missing observations as unknown rather than zero so status checks aren't misreported.

Instructions

Read the published monitoring snapshot. Missing observations are not zero.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds one genuinely non-obvious behavioral trait that annotations cannot convey: missing observations are not zero, warning the agent against imputing absent datapoints as real zero values. It stops short of describing freshness, caching, or coverage of the snapshot.

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 short sentences with zero filler: the action is front-loaded, and the interpretive caveat follows immediately. Every sentence earns its place, and the terse style suits a zero-argument read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be explained, and rich annotations cover the safety profile. What remains thin is scope: the description never says what the snapshot covers (which metrics, which time window) or how it relates to the history/analytics siblings, leaving the agent to infer scope from the schema alone.

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 no parameter meaning the description needs to supply. The description correctly adds no redundant parameter prose, though it also cannot compensate for anything since nothing is missing.

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?

The description states a specific verb and resource ("Read the published monitoring snapshot"), so an agent knows this is a read of a precomputed/published monitoring view rather than a live query. It does not, however, distinguish itself from close siblings such as reliquary_monitoring_history or reliquary_monitoring_analytics, leaving the boundary implicit.

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

Usage Guidelines3/5

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

Usage is only implied: the word "published" suggests this returns an already-materialized snapshot rather than a recomputation, which nudges the agent away from the analytics/history siblings. There is no explicit when-to-use, when-not-to-use, or named alternative, and the second sentence is a data caveat rather than routing guidance.

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