Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_readiness

Read-onlyIdempotent

Check database and execution readiness while preserving upstream billing and availability gates, so workflows can verify prerequisites before running batch jobs.

Instructions

Read database and execution readiness, preserving upstream billing and availability gates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered by structured data. The description contributes the non-obvious point that upstream billing and availability gates are preserved rather than consumed, but it does not clarify what the gates mean, whether results can be stale, or what 'preserving' entails operationally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, and the core action is front-loaded. However, half the sentence is spent on an opaque qualifier ('preserving upstream billing and availability gates') that adds words without adding comprehension.

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 no parameters, an output schema, and full annotation coverage, the definition needs only to explain what 'readiness' encompasses and how it differs from the health/connection siblings. It gestures at that but leaves the central concept undefined, so it is adequate rather than complete.

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 nothing for the description to disambiguate; the empty object schema is self-explanatory. Baseline 4 applies.

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 verb+resource is identifiable ('Read ... readiness') and two domains are named (database, execution), but 'readiness' is never concretized into what is actually checked, and the trailing clause about 'upstream billing and availability gates' is unexplained jargon. It does not differentiate itself from plausible siblings such as reliquary_health or reliquary_connection.

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 statement of when to call this versus reliquary_health, reliquary_connection, or reliquary_monitoring_health, and no prerequisites or exclusions. Usage can only be guessed at from the word 'readiness'.

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