Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_monitoring_history

Read-onlyIdempotent

Read retained network-wide observations for 24h, 7d, or 30d views, returning monitoring history results with original source timestamps preserved.

Instructions

Read network-wide retained observations for 24h, 7d or 30d. Preserve source timestamps when reporting results.

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": {
      "view": "<view>"
    },
    "name": "reliquary_monitoring_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
rangeNo24h

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context the annotations do not: results are 'retained' observations bounded to 30 days, and source timestamps must be preserved when reporting. It does not say what happens to data older than the retention window or how large result sets are handled.

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?

Two short sentences with the capability stated first and the output-handling caveat second; nothing is padded. The only cost is that the leading 'network-wide' framing is imprecise given the view enum.

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 the annotations cover the read-only profile. What remains missing is material for a two-parameter tool: the meaning and selection criteria for each `view` value, which is the single decision the agent must make before calling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden, yet it never mentions the required `view` parameter at all — the four enum values (network, miners, chain, status) have no stated semantics. It only loosely covers `range`, and the phrase 'network-wide' arguably misdescribes a tool whose required parameter selects among non-network scopes.

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 and resource ('Read ... retained observations') with the supported time windows, so the agent knows it is a historical-read tool rather than a live one. However, 'network-wide' is narrower than the tool's own `view` enum (network/miners/chain/status) and there is no differentiation from siblings such as reliquary_monitoring_analytics or reliquary_monitoring_snapshot.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given; the mention of 24h/7d/30d is a capability constraint, not a routing rule. With four monitoring siblings in the catalog and no stated condition for choosing this one, the agent must infer the choice.

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