Skip to main content
Glama
RichardGuan1

EH Index MCP

by RichardGuan1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get popular galleries

eh_get_popular
Read-onlyIdempotent

Retrieve current popular galleries from E-Hentai or ExHentai. Choose the target site to control requests and base URLs for relative gallery links.

Instructions

List the current popular galleries from E-Hentai or ExHentai. The selected site controls both the request and the base URL used for relative gallery links. Use eh_search_galleries when query filters are needed instead of the site's popular ranking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoTarget site; gallery URLs override this when a URL is providede-hentai

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedOutput schema / properties / result / properties / galleries / items / properties / site
      Added value: +{
+  "enum": [
+    "e-hentai",
+    "exhentai"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / result / properties / galleries / items / required
      Previous value: -[
-  "gid",
-  "token",
-  "url",
-  "title",
-  "category",
-  "uploader",
-  "posted",
-  "pages",
-  "rating",
-  "tags",
-  "thumbnailUrl"
-]New value: +[
+  "gid",
+  "token",
+  "site",
+  "url",
+  "title",
+  "category",
+  "uploader",
+  "posted",
+  "pages",
+  "rating",
+  "tags",
+  "thumbnailUrl"
+]
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / site / description
      Added value: +"Target site; gallery URLs override this when a URL is provided"
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds a genuinely useful trait beyond that — the selected site drives both the request and the base URL for relative gallery links — though it does not mention result counts or pagination behavior.

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?

Three sentences, zero waste, with the core action front-loaded and the routing guidance placed last where a reader deciding between tools will find it.

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

Completeness5/5

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

An output schema exists and annotations cover the safety profile, so the description only needed to establish purpose, source selection, and sibling routing — all present. Nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 100% for the single enum'd site parameter, so the baseline is 3. The description goes further by explaining what the site value actually controls (request target and relative-link base URL), which the schema's own property text does not clearly convey.

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

Purpose5/5

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

States a specific verb and resource ('List the current popular galleries') and names the two supported sources, which distinguishes it immediately from the many eh_search_* siblings.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use eh_search_galleries when query filters are needed instead of the site's popular ranking.' The alternative and the condition selecting it are both stated, leaving nothing 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