Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_connection

Read-onlyIdempotent

Inspect configured access, write enablement, available tools, and supported workflows for Reliquary MCP to plan allowed actions; does not validate credentials or product availability.

Instructions

Discover configured access, write enablement, available tools and supported workflows. Does not validate credentials or product availability.

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

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral scope by stating what is discovered and by explicitly disclaiming credential validation and product availability, which helps set expectations beyond the annotations.

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?

The description is two sentences long, with the discovery scope front-loaded and the important limitation in the second sentence. There is no wasted wording.

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?

The tool has no parameters, rich annotations, and an output schema, so the description need not explain return values. It adequately covers what the tool discovers and what it does not validate, though it could better distinguish itself from nearby health, readiness, and catalog tools.

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, so there is no parameter meaning to explain. The schema description coverage is 100%, and the description appropriately focuses on the tool's purpose rather than on nonexistent inputs.

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 uses a specific verb, "Discover," and enumerates concrete resources: configured access, write enablement, available tools, and supported workflows. It is clear what the tool returns, but it does not distinguish itself from sibling tools such as reliquary_health, reliquary_readiness, or reliquary_catalog.

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?

The description implies usage for initial discovery and adds an explicit exclusion: "Does not validate credentials or product availability." However, it gives no positive when-to-use guidance and does not name an alternative tool for credential or availability checks.

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