Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_evaluation_catalog

Read-onlyIdempotent

Read available evaluation sets, modes, and current ordering limits before requesting a quote for GPU batch evaluation workflows.

Instructions

Read qualified evaluation sets, modes and current ordering limits before requesting a quote.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds that the returned values are 'current', implying they change over time and should be re-read rather than cached, but it says nothing about auth requirements, rate limits, or what 'qualified' filters out.

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?

A single front-loaded sentence with no filler; the prerequisite framing ('before requesting a quote') is placed at the end where it reads naturally. Minor deduction because 'qualified' is unexplained jargon that occupies space without resolving meaning.

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

Completeness3/5

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

With an output schema present and zero parameters, the description does not need to explain return values, which lowers the burden considerably. Still, the core nouns (evaluation sets, modes, ordering limits) and the relationship to the 'quote' step are undefined, leaving the agent to infer what it will actually receive.

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 baseline is 4; there is no parameter meaning the description could add. The description correctly signals a parameterless call by not implying any required input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Read') and lists resources ('evaluation sets, modes and current ordering limits'), which is more specific than the tool name alone. However, the resources are domain jargon ('qualified evaluation sets', 'modes') that an agent cannot map to concrete data, and nothing distinguishes it from sibling catalog tools such as reliquary_catalog or reliquary_compute_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?

'before requesting a quote' gives a genuine sequencing cue, telling the agent this is a prerequisite read step rather than an action tool. There is no explicit when-not guidance and no named alternative, so the usage context is implied rather than stated.

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