Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_network

Read-onlyIdempotent

Read the published public network projection with freshness and provenance to inspect current Reliquary network state.

Instructions

Read the published public network projection with freshness and provenance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description is not required to restate safety. It does add context beyond them by disclosing that the payload is a 'published' projection carrying freshness and provenance, which tells the agent the data is a snapshot with trust metadata rather than a live query result. It omits any statement of auth requirements, rate limits, or whether the projection can go stale.

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?

A single eleven-word sentence, front-loaded with the verb and resource, with the freshness/provenance payload note trailing. No filler or redundant restatement of the title.

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

Completeness4/5

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

With no input parameters, rich annotations, and an output schema documenting the response, the description is close to sufficient. The remaining gap is that it never explains what 'freshness' means operationally (e.g. staleness bounds or whether results are cacheable), which an agent choosing among snapshot-style siblings would want.

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 zero parameters (additionalProperties: false), so there is nothing for the description to disambiguate; the schema itself is fully closed. No parameter meaning is lost.

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 names a specific verb ('Read') and a specific resource ('the published public network projection'), so the agent knows this returns a network-level dataset rather than catalogs or health data. It stops short of explicitly contrasting with the many sibling catalog/inventory/monitoring tools, and 'network projection' remains somewhat jargon-dependent.

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 qualifiers 'published' and 'public' suggest this is the consumer-facing snapshot rather than an internal or draft view. There is no explicit when-to-use guidance, no statement about when another sibling tool (e.g. inventory or catalog) would be preferred, and no caveats about freshness window.

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