Skip to main content
Glama
Reliquary MCP

Reliquary MCP

Official
by reliquadotai

reliquary_affine_batch_review

Read-onlyIdempotent

Review inline Affine v1/v2 batch JSON and raw mining.json locally to inspect structure, prefix cap counts, and exact byte hashes without network access, uploads, or execution.

Instructions

Locally review inline official Affine v1/v2 batch JSON and raw mining.json (each at most 1 MiB). Returns structure, prefix cap counts and exact byte hashes. Full official tokenizer validation remains not_run. No network, paths, credentials, upload or execution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "batchJson": "<batchJson>",
      "miningJson": "<miningJson>",
      "hotkey": "<hotkey>"
    },
    "name": "reliquary_affine_batch_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotkeyYes
batchJsonYes
miningJsonYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add limits and non-capabilities, which it does well: the 1 MiB per-input cap, the explicit 'no network, paths, credentials, upload or execution' scope, and the disclosure that tokenizer validation is not performed. The only gap is it does not say how inputs are rejected at the size boundary or what failure modes look like.

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?

Four dense sentences, front-loaded with the action and inputs, followed by return content and then the negative scope. No filler; the compressed phrasing ('Full official tokenizer validation remains not_run') costs a little readability but wastes no space.

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?

An output schema exists, so the brief mention of returns (structure, prefix cap counts, byte hashes) is supplementary rather than required. The description covers limits and non-capabilities well, but with 0% schema coverage the unexplained required hotkey parameter is a genuine completeness hole for a three-required-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three required parameters, so the description carries the full burden. It clarifies that batchJson and miningJson are inline JSON payloads subject to a 1 MiB cap, but the required 'hotkey' parameter (with a pattern constraint) is never mentioned at all, leaving an agent to guess its role.

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 gives a specific verb ('Locally review') and names both resources precisely ('inline official Affine v1/v2 batch JSON and raw mining.json'), plus the scope constraint of 1 MiB each. It is distinguishable from the sibling reliquary_affine_batch_plan by the review-vs-plan framing, though it never names that alternative explicitly.

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?

'Locally review inline ... JSON' implies the usage context (you already hold the payloads in-memory and want an offline inspection), and the note that full tokenizer validation 'remains not_run' hints this is a lighter check. But there is no explicit when-to-use/when-not statement and no named alternative for heavier validation.

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