Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_monitoring_analytics

Read-onlyIdempotent

Read a published Reliquary analytics view with bounded filters to inspect public network, mining, training, and evaluation evidence without accessing owned customer tasks.

Instructions

Read one published analytics view with bounded published filters. This is public evidence, separate from owned customer tasks.

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_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNo
runNo
hashNo
laneNo
taskNo
viewYes
domainNo
hotkeyNo
offsetNo
windowNo
coldkeyNo
hotkeysNo
verdictNo
windowsNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

C2.9/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 safety is covered. The description adds that results are "public evidence, separate from owned customer tasks," which is real scope information, but vagueness about what "bounded" means and silence on pagination (relevant given the offset/window params) limit the value added.

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 core action front-loaded and no redundant restatement of the name. The second sentence is terse to the point of being cryptic, but no wording is wasted.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 14 parameters, 22 view values and 4 enums, the definition is far too thin; the output schema covers return values, but filter-to-view applicability and pagination are undocumented. An agent could call it, but only by guessing which filters each view accepts.

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% across 14 parameters, so the description carries the full explanatory burden and largely fails it. It never explains view semantics, the offset/window paging model, or which of job/run/hash/lane/domain/hotkey/coldkey/verdict apply to which view — only a generic mention of "published filters."

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?

"Read one published analytics view" gives a specific verb and resource with a clear scope of exactly one view. It does not differentiate itself from siblings such as reliquary_monitoring_snapshot or reliquary_monitoring_history, and "analytics view" stays abstract despite 22 enumerated view values.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives among the monitoring siblings. The phrase "bounded published filters" hints at a filter restriction but does not state which combinations are valid, so the agent must infer selection from the schema alone.

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