Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_run_catalog

Read-onlyIdempotent

Lists published public training runs and their stored availability so you can select valid run identifiers, while customer tasks remain separately scoped.

Instructions

List published public training runs and their stored availability. Use only returned run identifiers; customer tasks remain separately scoped.

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

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?

The annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description is not obligated to re-state safety. It adds genuinely new context beyond them: that only published/public runs appear, that customer tasks live in a separate scope, and that only returned identifiers should be used downstream. It stops short of noting result size or pagination for what could be a large catalog.

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?

Two short sentences, with the core listing behavior front-loaded and the identifier constraint following. Every clause carries a distinct instruction; nothing is redundant padding.

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?

For a zero-parameter read tool with a full output schema and complete annotation coverage, the description supplies the essential missing pieces: visibility scope and identifier provenance. Only the absence of guidance relative to reliquary_run_monitor keeps it below a 5.

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 and the schema is empty with additionalProperties false, so there is no parameter meaning for the description to add. Baseline 4 applies; the description correctly spends no words 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 ('List') with a precisely scoped resource ('published public training runs and their stored availability'), so an agent knows exactly what comes back. It does not name the nearest sibling (reliquary_run_monitor) to contrast live monitoring against this static catalog, so differentiation is only implicit.

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 clause 'Use only returned run identifiers' is a real usage constraint that steers the agent's downstream calls, and 'customer tasks remain separately scoped' implies a boundary. However, there is no explicit statement of when to pick this tool over the sibling run_monitor or other catalog tools, leaving the choice to inference.

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