Skip to main content
Glama
RichardGuan1

EH Index MCP

by RichardGuan1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Resolve galleries from image pages in batch

eh_resolve_gallery_batch
Read-onlyIdempotent

Resolve up to 500 image-page references into gallery tokens through the official API, preserving input order and duplicates, and return per-input success and error counts.

Instructions

Resolve 1-500 image-page references to gallery tokens through the official API, preserving input order and duplicates. Returns per-input results with input, success, and error counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoTarget site; gallery URLs override this when a URL is providede-hentai
pagesYes1-500 image-page references to resolve

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
errorCountYes
inputCountYes
successCountYes
preservedOrderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • changedOutput schema / properties / errorCount / minimum
      Previous value: -0New value: +-9007199254740991
    • changedOutput schema / properties / inputCount / minimum
      Previous value: -0New value: +-9007199254740991
    • changedOutput schema / properties / successCount / minimum
      Previous value: -0New value: +-9007199254740991
  2. Changed5 schema fields changedv0.2.0
    • addedOutput schema / properties / errorCount
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / inputCount
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / preservedOrder
      Added value: +{
+  "const": true,
+  "type": "boolean"
+}
    • addedOutput schema / properties / successCount
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "inputCount",
+  "successCount",
+  "errorCount",
+  "preservedOrder"
+]
  3. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / pages / description
      Added value: +"1-500 image-page references to resolve"
    • addedInput schema / properties / site / description
      Added value: +"Target site; gallery URLs override this when a URL is provided"
  4. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: input order and duplicates are preserved, and the call returns per-input results with success/error counts, implying partial failures do not abort the batch. It does not mention rate limits or auth needs for the official API path.

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, both front-loaded with the core operation and its guarantees, with no repetition. 'Through the official API' is mild filler but the rest earns its place.

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 an output schema present, return-value detail is not required, and the description still summarizes the result shape (per-input input/success/error counts). Batch limits, ordering and duplicate handling are covered; only alternative-tool routing and any API/auth caveats are absent.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents site, pages, gid, page and pageToken including formats and constraints. The description adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 ('Resolve') and resource ('image-page references to gallery tokens') plus the batch scope (1-500), so the operation is unambiguous. It never names the singular sibling eh_resolve_gallery, leaving the agent to infer the batch/single split from the name and limit alone.

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?

The 1-500 range implies this is the bulk path, and 'preserving input order and duplicates' hints at when bulk resolution is appropriate. However, there is no explicit when-to-use or when-not-to-use guidance relative to eh_resolve_gallery or any alternative, so the routing decision is left to inference.

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

Deploy Server

Other Tools