Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_generation_catalog

Read-onlyIdempotent

Read qualified generation models, sources, environments and limits, plus accepted model architectures, before requesting a GPU compute quote.

Instructions

Read qualified dataset generation models, sources, environments and limits before requesting a quote. architectures lists the model architectures (config.json architectures[0]) that pinned-model, batch file and evaluation quotes accept, or null before the platform has read the list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine behavioral nuance beyond that: 'qualified' implies pre-filtered eligible entries, and 'architectures' may be null before the platform has read the list, warning of a state-dependent response. It does not cover pagination or refresh timing, keeping it at 4.

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 sentences, front-loaded with the purpose and the 'before requesting a quote' trigger. The second sentence is dense but each clause carries information; no filler or restatement of the tool name.

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

Completeness5/5

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

With zero parameters, an output schema present, and annotations covering the safety profile, this description supplies everything an agent needs: what is returned, when to call it in the quote workflow, and how to interpret the possibly-null architectures field.

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 the schema carries no semantic burden and the baseline is 4. The description's discussion of 'architectures' refers to returned data rather than inputs, so it adds nothing on the parameter axis.

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?

States a specific verb ('Read') and enumerates the resource set: generation models, sources, environments, and limits. The 'generation' qualifier implicitly separates it from the sibling evaluation/compute/run catalogs, though no sibling is named explicitly for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear sequencing constraint: read this 'before requesting a quote.' That tells the agent exactly where this call belongs in a workflow. It stops short of naming alternative catalogs or stating when not to call it, so it does not reach a 5.

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