Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_compute_catalog

Read-onlyIdempotent

Compare public GPU compute offers and provider observations to evaluate available options; a listed offer does not authorize provisioning or rental.

Instructions

Compare public compute offers and provider observations. A listed offer does not authorize provisioning or rental.

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_compute_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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered structurally. The description adds one genuinely useful non-annotation fact — that inclusion in the catalog does not authorize provisioning or rental — but says nothing about data freshness, where "provider observations" come from, or whether results are live or cached.

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 no filler, and the core purpose is front-loaded ahead of the caveat. Nothing repeats the tool name or the annotations.

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?

With zero parameters, a present output schema, and full annotation coverage, the description needs only to state scope and purpose, which it largely does. The residual gap is the undefined term "provider observations" and the absence of any hint about the comparison's basis or freshness, which matters for an open-world tool.

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 semantics to explain and the baseline of 4 applies. The description correctly avoids inventing filter or scope arguments that the schema does not have.

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?

"Compare public compute offers and provider observations" gives a verb (compare) and a resource (compute offers), so the gist is recoverable. But "provider observations" is undefined jargon and nothing distinguishes this from the many sibling catalog tools (reliquary_catalog, reliquary_evaluation_catalog, reliquary_generation_catalog), so an agent cannot confidently choose it over them from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no named alternative. The second sentence is a legal/authorization caveat rather than routing guidance, so an agent gets no help deciding when this tool is the right call versus a sibling catalog tool.

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