Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_skills

Read-onlyIdempotent

Discover official workflow skills and their documentation, including access requirements, state, and install options. Filter by ID, state, category, or search to find available or upcoming products.

Instructions

Discover official workflow skills and their documentation, access requirements, state and install options. state not-yet-available marks a product that is not open yet; its availability note says what to use instead. Optional filters combine; unknown IDs or categories return an empty list. Reads the installed catalog without network access, credentials or execution.

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

Input Schema

NameRequiredDescriptionDefault
idNo
stateNonot-yet-available lists workflows whose product is not open yet.
searchNo
categoryNo

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, non-destructive, and closed-world, so the safety bar is pre-met. The description still adds real context beyond them: reads the installed catalog, requires no network access, credentials, or execution, and returns an empty list rather than erroring on unknown IDs. It does not describe pagination or result volume.

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?

Four compact sentences, each carrying distinct information: capability, state semantics with fallback, filter behavior and edge case, and the no-network/no-credential guarantee. Nothing is repeated from the schema or annotations, and the core capability is front-loaded.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description fills the remaining gaps – access requirements, state semantics, filter combination, empty-result behavior, and the absence of side effects. Only the search parameter's semantics are unaddressed.

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?

With only 25% schema description coverage across 4 parameters, the description must carry weight, and it does: it explains combining filters, the meaning of the not-yet-available state value, and the empty-list result for unknown id or category values. The 'search' parameter is left entirely unexplained, keeping it from a 5.

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 opens with a specific verb and resource: 'Discover official workflow skills and their documentation, access requirements, state and install options.' An agent can tell this is a skills/workflow catalog rather than a run, health, or monitoring tool, though no sibling is named to sharpen the boundary with the other catalog-style tools.

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?

It states that 'Optional filters combine' and that 'unknown IDs or categories return an empty list', which tells the agent how filtering behaves. It also explains the not-yet-available state and where to find the substitute. However, it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives, leaving selection to inference.

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