Skip to main content
Glama
RichardGuan1

EH Index MCP

by RichardGuan1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search by image SHA-1

eh_search_by_hash
Read-onlyIdempotent

Find E-Hentai or ExHentai galleries by an exact 40-character SHA-1 image hash without uploading the image.

Instructions

Search E-Hentai by an exact 40-character SHA-1 image hash without uploading the image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sha1YesExact 40-character hexadecimal SHA-1 hash of an image
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. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / sha1 / description
      Added value: +"Exact 40-character hexadecimal SHA-1 hash of an image"
    • 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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and repeatability profile is covered. The description only adds the no-upload detail and exactness of the match; it says nothing about result behavior on a miss or pagination.

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?

One tightly written sentence with the verb, resource, input constraint, and differentiator all front-loaded. No filler.

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?

An output schema exists and the annotations carry the safety profile, so the description need not explain return values. For a simple two-parameter lookup it is nearly complete, though nothing is said about the site override behavior mentioned in the schema.

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 both sha1 and site are fully documented in the schema. The description merely restates the hash format already given in the sha1 description and says nothing about the site parameter, so baseline 3 applies.

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 (Search), resource (E-Hentai by image SHA-1 hash), and the exact input constraint (40-character hash). The phrase 'without uploading the image' distinguishes it from the sibling eh_search_by_file, which is the closest alternative.

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

Usage Guidelines4/5

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

The 'without uploading the image' clause implicitly tells the agent to choose this over an upload-based search when a hash is already known. No explicit when-not condition or named alternative is given, so it falls short of a 5.

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